"Error updating component prop" #11212
-
|
Hi folks, "Error updating component prop" Latest version: 2.8.10. also 2.8.2 was not working ( self hosted ) What is the reason for this? I am able to change / edit some of my screens but some not!? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
|
Hey @JohannesM007 It is possible that your app database has become conflicted somehow. Are you able to follow the steps outlined here? #7777 (comment) If not feel free to email a download link of your app export to support@budibase.com and I can take a look if you wish. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @melohagan, |
Beta Was this translation helpful? Give feedback.
-
|
Hey @JohannesM007, Firstly thank you for providing the app export. This was very helpful. I've gone through and had a look at the screens you highlighted in the screenshot above, below is a list of how I fixed them. The general answer to all the issues you are experiencing is that you are nesting components that shouldn't be nested inside one another. With the last update validation that was previous not working was fixed meaning that going forward illegal nesting such as the below can no longer be done.
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your feedback, so i guess i have to redesign all this screens. Bad news but i will try to fix it. |
Beta Was this translation helpful? Give feedback.
-
|
@melohagan I am having the same problem now after upgrading my self-host to from v2.1.24 to v2.8.10, even after I cleaned up all conflicts on DB table as explained on #7777. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @dannyshin76, You are right going forward there are certain components that can no longer be nested inside one another. Forms is one of these components. Another would be side panels inside another side panel. I hope this makes sense! |
Beta Was this translation helpful? Give feedback.
-
|
That is a bad news, because it means many users (including me) will have to completely rewrite many pages with nested forms. I don't know other people's use case but for me, I have to use nested forms to implement a mean to share or communicate information between forms. Also I can't mangle multiple forms into one because in my use case, one form must represent a single JSON object with schema. So I would like to suggest a designer option to disable that validation. Will it be possible? I am asking this because my nested forms are being executed without problem even with the most recent upgrade. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @dannyshin76, You should be able to nest forms that are contained within a side panel (Meaning you still have access to the previous forms data). If you are self-host you can revert back to before the most recent (v2.7) update were this validation wasn't turned on. Additionally, you may be able to use the custom form schema option to map out all your data before it is submitted. I hope this helps. |
Beta Was this translation helpful? Give feedback.
-
|
OK, thanks for your information. For now I guess I have no choice but to revert BB version to v2.7.x. I see v2.7.38 is the last one before upping to v2.8.x. Is this version OK? |
Beta Was this translation helpful? Give feedback.
Hey @JohannesM007,
Firstly thank you for providing the app export. This was very helpful. I've gone through and had a look at the screens you highlighted in the screenshot above, below is a list of how I fixed them.
The general answer to all the issues you are experiencing is that you are nesting components that shouldn't be nested inside one another. With the last update validation that was previous not working was fixed meaning that going forward illegal nesting such as the below can no longer be done.