Fields visibility in forms - disabled or hidden fields due to configuration key
Symptom
Some standard fields in forms are not displayed in the UI. In general, the first thing that I will look at is the property Visible of the element in the form design. If a form element has property Visible = No, the element will not be visible in the UI.
Sometimes, the visibility of a form element can also be controlled via codes. This scenario will be explored in another post.
Here in this article, I want to share the example of disabled or obsolete elements indicated by their Configuration Key property.
Example scenario
In SalesTable form, some fields under are not shown
- Sales order header -> Delivery tab -> added fields standard in the carrier info group not showing
- Sales line details -> Address tab -> Delivery contact and Address sales responsible fields
Reason
All these missing fields are depreciated or locked so they are not available to use.
These fields are not available to be used anywhere. If you search for references of these fields in VS, you’ll see that there are no references of any data entities. Thus, they shouldn’t be used for DIXF or integration. They probably still exist in some forms and tables due to design or regression reasons but again they won’t be used.
For CarrierInfo in header view, there are 5 disabled fields. We check these fields in the source SalesTable. Three of them have ShipCarrier as configuration key and this key cannot be enabled.
ShipCarrier configuration key cannot be enabled
The other 2 fields have SysDeletedObjects72 as configuration key, which indicates depreciated fields.
For ShipCarrierLineAddress in line view, the whole group is not available because it has ShipCarrier as configuration key.
