[Explore] Right after DataModel Creation/Update, the BQ layer shows an Data Configuration Failed message
Description
PRDE - Bug default text according to the team DoR (Definition of Ready)
01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
@Douglas Coimbra Lopes
02 - PROBLEM (WHAT'S THE ISSUE?):
- When a new data model is created/updated, an error occurs on the Explore BQ layer when we try to see the records
- The notification schema tasks are not failed, however, the mdmBQSynchronizationStatius seems to be FAILED
- If we refresh the screen, it seems the problem is solved
- Scenarios to be reproduced
- DM Creation/Update through UI
- DM Creation via upload Snapshot
- DM Creation/Update via Installation Carol App
03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):- SCENARIO1: DM CREATION/UPDATE VIA UI
- Create a DM using UI
- Publish it
- Go to Explore
- Switch to the BQ layer message to access the view
- SCENARIO2: DM SNAPSHOT
- Create/Update a DM using upload Snapshot
- Publish it
- Go to Explore
- Switch to the BQ layer message o access the view
- SCENARIO3: DM CREATION/UPDATE VIA CAROL APP INSTALL/UPDATE
- Create/Update a DM
- Publish it
- create a new tenant
- Release the app for install
- Approve & install the app
- Go to Explore
- Switch to the BQ layer message o access the view
04 - LINKS (ADD A LINK TO THE BUG OR TO THE TENANT):
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):- No failed scenario if the task finishes successfully.
Activity
Show:
Details
Priority
HighestAssignee
Carlos Affonso Wagner
Reporter
Robson Thanael Poffo
Labels
CAROL_BACKLOG_REVIEWPLANNED
Due Date
1 January 2024
Fix versions
CAPL_3.97
Components
DATA_MODEL | VIEW
Created
3 November 2023, 10:11
Updated
20 February 2024, 12:51
More fields
Created: 3 November 2023, 13:11
Updated:
20 February 2024, 15:51
This issue was automatically transitioned to DONE after being deployed to production on Github.
https://github.com/totvslabs/carol-ui/releases/tag/v4.39.0
No associated issue on JIRA TOTVS BRAZIL.
@Robson Thanael Poffo ,
@Pedro Buzzi , @Carlos Affonso Wagner , @Andre Pasold , @Chámam Diomede Caires
This issue was planned to be delivered until 2024-01-01. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-12-11, 2024-01-01
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master branch in Github).
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by andregp.
SCENARIO1: DM CREATION/UPDATE VIA UI
SCENARIO2: DM SNAPSHOT
SCENARIO3: DM CREATION/UPDATE VIA CAROL APP INSTALL/UPDATE
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
fix(DM): https://totvslabs.atlassian.net/browse/CAPL-4962#icft=CAPL-4962 update DM after schema change
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera , @Carlos Affonso Wagner ,
This issue was planned to be delivered until 2023-12-11. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-12-11
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
FE should check if the app is updating the DataModel after the task about Change_Schema is complete.
If so, check if the bqSyncStatus on the DataModel is already update