The checkbox becomes disabled when any modifications are applied to the detail schema in configurations, such as comments, custom methods, attributes, etc. This behavior is determined by the _canChangeType method in the DetailDesignerUtils module. The logic ensures that when the checkbox is disabled, the wizard does not save modifications applied to the base detail with a list schema, preventing any loss of changes.
This logic cannot be overridden, which is why the detail cannot be switched from an editable list detail to a standard detail if schema modifications are present.
To address this issue, you can choose one of the following approaches:
Remove the custom code, including comments, and save the changes. This will make the checkbox available again in the detail wizard.
Delete all methods and values associated with the edited detail's features from the detail schema. This will make the detail non-editable.
We would also like to highlight that this logic has been improved in the new FreedomUI designer. The updated designer addresses these nuances, allowing you to modify the attribute of the edited pattern with a single setting, without requiring additional code changes.
The checkbox becomes disabled when any modifications are applied to the detail schema in configurations, such as comments, custom methods, attributes, etc. This behavior is determined by the _canChangeType method in the DetailDesignerUtils module. The logic ensures that when the checkbox is disabled, the wizard does not save modifications applied to the base detail with a list schema, preventing any loss of changes.
This logic cannot be overridden, which is why the detail cannot be switched from an editable list detail to a standard detail if schema modifications are present.
To address this issue, you can choose one of the following approaches:
Remove the custom code, including comments, and save the changes. This will make the checkbox available again in the detail wizard.
Delete all methods and values associated with the edited detail's features from the detail schema. This will make the detail non-editable.
We would also like to highlight that this logic has been improved in the new FreedomUI designer. The updated designer addresses these nuances, allowing you to modify the attribute of the edited pattern with a single setting, without requiring additional code changes.
I have a detail that has been added on an opportunity in code, so I cannot make it read-only with the opportunity designer. How do I set up the code so that make a decimal field in the detail read-only ?
I have created a editable GRID and added some business rule . I have added few field as read only but still i was able to edit in the editble GRID . Any idea what is causing this problem ?
I would like to suggest you to check the below articles where you can find the requested information, as well we have a lot of useful posts on community on this topic: