hi I created a support table to check the conditions before adding the row to the DOCUMENTS table but now I ask you if I have to correct this data I have to read it directly from the DOCUMENTS table and I can no longer modify it taking into account the various conditions. How can I get around the problem? I would like the changes to pass through the same support table or an equal one that checks the conditions first and if everything is ok then makes the correction to the DOCUMENTS table.
1 Like
Create a âSingle Valueâ â âWhole Rowâ column in your Documents table that points back to the Support table. Then change your edit button to a workflow that updates values in the Support table through the Single Value column, followed by navigating to the Support table detail screen.
You will also need to add a flag in the Support table so you know if you are in Add or Edit mode. Then change your support screen submit button to either add a new row or update the existing row in the Documents table based on that flag. You will also need a relation from the Support table back to the matching row in the Documents table to do that update.
2 Likes
Just confirming your problem here:
- You created a Support table (like a helper table) to check conditions before adding data to the DOCUMENTS table.
- When you need to correct or edit existing data, you have to access it directly from the DOCUMENTS table.
- This direct editing bypasses the condition checks in the Support table, which I assume can only be done in a âcustom formâ environment and not in an edit screen.
- You want all changes - including corrections - to go through the Support table (or a similar process) so that conditions are always checked before updating the DOCUMENTS table.
Can you let us know what type of checks do you need to happen in the support table that is not possible in an edit form?
1 Like
I managed to do everything, I created a button that adds a new row to Orders with the data from the selection table and then sends the change. Now Iâve run into another problem when I go to the user details and the possibility of changing the contents of the fields even before pressing the button that moves it to the orders row. How can I prevent this? Thanks.
Wouldnât it mean you have two rows of the same âentityâ if this means adding a row for every edit?
Iâm not sure why youâre not using the native edit screen for this, what type of validation that it doesnât support?
Or do you want to have a log of values every time an entity is edited?
Because the native modification does not allow me to propose the choice of dishes based on the date and does not allow me to check if the modification is made within the permitted times. However, with the support table I solved both the new order and the modification pass from there and then I delete the row. It seems that everything works well for me, the only flaw is the fact that I cannot block the modification in the details sheet.
Do you mean these are the same problem? Are you using entry components in the details screen?
