-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Variables tab crash after setting Objects API registration. #5031
Open
LaurensBurger opened this issue
Jan 23, 2025
· 3 comments
· Fixed by #5021 · May be fixed by #5150 or #5152
Open
Variables tab crash after setting Objects API registration. #5031
LaurensBurger opened this issue
Jan 23, 2025
· 3 comments
· Fixed by #5021 · May be fixed by #5150 or #5152
Labels
Milestone
Comments
10 tasks
Bob seems to experience this still on 3.0.2 |
Refinement: Blocked until DH gives us details when this happens. |
Workaround is throw registration backend away :D |
robinmolen
added a commit
that referenced
this issue
Mar 11, 2025
robinmolen
added a commit
that referenced
this issue
Mar 11, 2025
…bjects API registrations Due to a previously missing default value, some (older) Objects API registrations might not have `variables_mapping` in their `options` configuration. This causes issues when trying to configure variables to the Objects API, resulting in javascript errors. This script ensures that all Objects API registrations have, at least, an empty array as `options` `variables_mapping`.
robinmolen
added a commit
that referenced
this issue
Mar 11, 2025
robinmolen
added a commit
that referenced
this issue
Mar 11, 2025
…bjects API registrations Due to a previously missing default value, some (older) Objects API registrations might not have `variables_mapping` in their `options` configuration. This causes issues when trying to configure variables to the Objects API, resulting in javascript errors. This script ensures that all Objects API registrations have, at least, an empty array as `options` `variables_mapping`.
10 tasks
robinmolen
added a commit
that referenced
this issue
Mar 11, 2025
Any form with an Objects API registration V2 (the variable mapping), that doesn't have `variables_mapping` in the `options` config, will have its `variables_mapping` set to empty array. Due to a previously missing default value in the Objects API registration, the `options` value `variables_mapping` could be missing. If missing, this would cause javascript errors in during the variable mapping in the admin.
robinmolen
added a commit
that referenced
this issue
Mar 11, 2025
…_mapping options When importing a form with an Objects API registration, that doesn't have a version, the version is set to 2. And based on the version of the Objects API registration, a default value for `variables_mapping` is set.
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
…bjects API registrations Due to a previously missing default value, some (older) Objects API registrations might not have `variables_mapping` in their `options` configuration. This causes issues when trying to configure variables to the Objects API, resulting in javascript errors. This script ensures that all Objects API V2 registrations have, at least, an empty array as `options` `variables_mapping`.
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
Any form with an Objects API registration V2 (the variable mapping), that doesn't have `variables_mapping` in the `options` config, will have its `variables_mapping` set to empty array. Due to a previously missing default value in the Objects API registration, the `options` value `variables_mapping` could be missing. If missing, this would cause javascript errors in during the variable mapping in the admin.
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
…_mapping options When importing a form with an Objects API registration, that doesn't have a version, the version is set to 2. And based on the version of the Objects API registration, a default value for `variables_mapping` is set.
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
The V1 Objects API registration should not have the `variablesMapping` property. This will result in error when validation in the backend.
10 tasks
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
…bjects API registrations Due to a previously missing default value, some (older) Objects API registrations might not have `variables_mapping` in their `options` configuration. This causes issues when trying to configure variables to the Objects API, resulting in javascript errors. This script ensures that all Objects API V2 registrations have, at least, an empty array as `options` `variables_mapping`.
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
Any form with an Objects API registration V2 (the variable mapping), that doesn't have `variables_mapping` in the `options` config, will have its `variables_mapping` set to empty array. Due to a previously missing default value in the Objects API registration, the `options` value `variables_mapping` could be missing. If missing, this would cause javascript errors in during the variable mapping in the admin.
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
…_mapping options When importing a form with an Objects API registration, that doesn't have a version, the version is set to 2. And based on the version of the Objects API registration, a default value for `variables_mapping` is set.
robinmolen
added a commit
that referenced
this issue
Mar 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Product versie / Product version
3.0.1
Customer reference
DH
Omschrijf het probleem / Describe the bug
After setting registration > Objects API (variable mapping). The variables tab in the from crashes:
Previously mapped, or imported forms with "variables_mapping" do not show this behavior.
The text was updated successfully, but these errors were encountered: