Skip to main content
December 26, 2023
Question

Unable to insert record in db Mapping table with relationship many to one table in one go

  • December 26, 2023
  • 16 replies
  • 0 views

As above table having many to one relationship we can see as arrow, we are considering Mapping table as master table, All tables we have created Record type.

1. in one UI page used "Mapping table", and in that page we are selecting Country, Region and Category code. Entering textbox values of "Info table" and "Att table"

and clicking "Submit" button. We are getting error.

"function a!dropdownField [line 33]: An error occurred while executing a save: Expression evaluation error: Field with [identifier=9b2cef30-2e3c-4575-9e32-c9897a6dff7a] not found on the Record Type"

2. Here we need to insert same record in "Info table" and "Att table" once done then new both Ids need to insert in "Mapping table" how we can do in one go on click of submit button?

"The input "Records" cannot be created or updated. The relationship configuration between "Mapping table" and "Att table" is set to 'Do not allow updates'. Location of the error: " Mapping[1].Att table"

Please help me here to rectify this problem."

    16 replies

    December 26, 2023

    Hi,

    For the first error, could you please share the code snippet of the dropdown field if it hasn't been fixed yet?

    For the second error, make sure to enable write and delete related records in the relationship configuration. Refer to the screenshot below:



    December 26, 2023

    Thanks for your reply.

    Please refer earlier attached snapshot, then you will get proper requirement. Since multiple tables entry values i need to insert in mapping table.

    December 26, 2023

    Let me understand your question again. Are you facing issues on the interface or on the process model? Are these two different errors?

    January 2, 2024

    Till now i did not got any proper solution for the same

    abhayd3663
    January 18, 2024

    I did not understand the problem statement completely however on high level I can say that the db design needs to be simplified to avoid such issues.