[Data Model] When the user tries to update the label/description from a children nested/object field, an error message is displayed

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 the user tries to update label/description from a nested/object children field, an error message displays

03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):

  • Access any data model with a Nested/ Object field + children fields
  • Edit Label/Description from any nested field from the Object/Nested field
  • Click on the Save Button
  • curl 'https://totvsregressions.qarol.ai/api/v1/entities/templates/3b2733adc71240c1a3b88e12c31a80e4/field/1a5ea4d36a574f31b0e7e9b2e1e5a113' \
      -X 'PUT' \
      -H 'authority: totvsregressions.qarol.ai' \
      -H 'accept: application/json' \
      -H 'accept-language: en-US,en;q=0.6' \
      -H 'authorization: b88259946c354a359b4b09beec8364c0' \
      -H 'content-type: application/json' \
      -H 'cookie: authorization-totvslabs=b88259946c354a359b4b09beec8364c0' \
      -H 'origin: https://totvsregressions.qarol.ai' \
      -H 'referer: https://totvsregressions.qarol.ai/totvslabs/carol-ui/datamodels/mdmproduct/fields/0a8443c0565547238ba7eee0ff084dc5.1a5ea4d36a574f31b0e7e9b2e1e5a113' \
      -H 'sec-ch-ua: "Not_A Brand";v="8", "Chromium";v="120", "Brave";v="120"' \
      -H 'sec-ch-ua-mobile: ?0' \
      -H 'sec-ch-ua-platform: "macOS"' \
      -H 'sec-fetch-dest: empty' \
      -H 'sec-fetch-mode: cors' \
      -H 'sec-fetch-site: same-origin' \
      -H 'sec-gpc: 1' \
      -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36' \
      --data-raw '{"mdmCustomDescription":{"en-US":"QuantityQA","pt-BR":"Quantidade","es":"Quantidad"},"mdmCustomEnumValues":null,"mdmCustomLabel":{"en-US":"QuantityQA","pt-BR":"Quantidade","es":"Quantidad"},"mdmEnableAddressCleansing":false}' \
      --compressed

Activity

Automation for Jira 22 March 2024, 10:28 Jira Internal Users

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).

Automation for Jira 19 March 2024, 14:20 Jira Internal Users

This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by felabs01,douglascoimbra.

Automation for Jira 19 March 2024, 14:20 Jira Internal Users

Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).

fix(datamodels): https://totvslabs.atlassian.net/browse/CAPL-5576#icft=CAPL-5576 editing nested fields not working

Douglas Coimbra Lopes 19 March 2024, 14:19 Jira Internal Users

DESCRIPTION SAVED

Automation for Jira 14 March 2024, 14:06 Jira Internal Users

This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.

Automation for Jira 13 March 2024, 11:10 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

fix(datamodels): https://totvslabs.atlassian.net/browse/CAPL-5576#icft=CAPL-5576 editing nested fields not working

Automation for Jira 1 March 2024, 19:01 Jira Internal Users

@MARCOS STUMPF ,
@Pedro Buzzi , @Carlos Affonso Wagner , @Carlos Affonso Wagner

This issue was planned to be delivered until 2024-03-25. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-03-01, 2024-03-25

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Automation for Jira 28 February 2024, 20:21 Jira Internal Users

@MARCOS STUMPF ,
@Carlos Affonso Wagner ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-03-01. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-03-01

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.