Loading...
Loading...
When a Form layout is opened in the Form Builder, if the form belongs to scope X while the session scope is set to Y, a cross-scope banner appears. However, after clicking “Edit in original scope” from the banner, any changes made in the Form Builder are not being saved.
Log in as an Admin and switch the instance scope to any scoped application. Create a new table or open an existing one from a Global or Custom Global App. Navigate to TB and click on Form. A banner will appear stating, “Different application scope. The form is in ”, along with the option “Edit in original scope.” Click Edit in original scope. Modify the form layout by adding or removing fields, then save your changes. Actual: Fields are not getting saved on Form layout Expected : Field should get save on the form layout without an issues seeing below error in network calls "{ "result": { "updated_on": "2024-12-13 11:35:05", "sys_id": "4e5b3c847fe65210a3cfbbf67c86656c", "children": [], "name": "Form Builder: Save", "state": "3", "message": "This editor was opened in the 'Global' application, but '<form_scope' is selected in your application picker. Switch to 'Global' to save.", "percent_complete": "100" } }"
Use the scope picker instead of "Edit in original scope" button in the Table Builder to switch the session scope to the one which is showing in the blue banner to make changes.
PRB1820975
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.