[Urgent] Cannot assign data fields to components anymore

[maveric1977]

Checklist

• I have searched budibase discussions and github issues to check if my issue already exists

Hosting

• Cloud
  • Tenant ID: modproductlibrary

Describe the bug
Every time I click on the lightning button for component properties, I receive the following error message in the browser console, and the page becomes completely non-functional:

Uncaught (in promise) InvalidCharacterError: Failed to execute 'add' on 'DOMTokenList': The token provided ('[object Object]') contains HTML space characters, which are not valid in tokens.
    at buildSectionHeader (index-ab4755b7.js:874:142)
    at index-ab4755b7.js:874:3464
    at Array.reduce (<anonymous>)
    at bindingsToCompletions (index-ab4755b7.js:874:3410)
    at to.$$.update (index-ab4755b7.js:879:25987)
    at init$3 (index-ab4755b7.js:4:11594)
    at new BindingPanel (index-ab4755b7.js:879:26449)
    at create_fragment$8J (index-ab4755b7.js:879:26724)
    at init$3 (index-ab4755b7.js:4:11650)
    at new ClientBindingPanel (index-ab4755b7.js:879:28378)

To Reproduce
Steps to reproduce the behavior:

1. Go to any of the designs in my productlibrary app
2. Select a form component
3. Click on the lightning icon next to a property
4. Nothing happens on the screen
5. Open the browser DevTools and open the console. You can see the error.
6. After this point the app does not respond to any other actions until a full page refresh is performed.

Expected behavior
The binding panel should open, letting the user select the binding from a list of fields and/or write a javascript code

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: macOS 15.1.1 (24B91)
• Browser chrome
• Version 131.0.6778.205 (Official Build) (arm64)

[linear]

BUDI-8968 [Urgent] Cannot assign data fields to components anymore

[aptkingston]

I've attempted to reproduce this but I'm unable to. Could you start from a blank screen and give exact instructions about how to reproduce this? Or even better if you'd be able to provide an app export which exhibits this behaviour.

[mikesealey]

@aptkingston I've got @maveric1977 's app-export, and hope to take a look later today. I'll keep you updated.

[ConorWebb96]

Hey @maveric1977,

The issue seems to be related to your type option picker field. Can you delete a re-add it again and make sure the form field name isn't lowercase type you can change it to anything else it just can't be this as its a resolved word.

Thanks.