We have a series of user defined check boxes added to the JobAsmbl_UD table. I recently had to add 3 additional check box fields. CheckBox21, 22 and 23. I added them, regenerated the data module several times, recycled IIS multiple times. The table is synced in the database. I added the additional check box controls to the Job Details – Assemblies – Assembly tab on the Job Entry form. The EpiBinding is selected for each of the 3 respective checkbox controls, however, when you run the form, these 3 controls will not allow changes. I have tried deleting and re-adding the controls and rebinding them to the fields, I have tried adding code to set readonly to false. Any ideas? Is there a limit to the number of check boxes you can add?
I checked the fields in the UD column maintenance screen against all the other check boxes to make sure all the properties were set the same. We are on version 10.2.300.
UD field names end with _c, except when they overlap with User fileds from prior versions. That’s why your Checkbox01 thru Checkbox20 don’t have a _c suffix.
I’m guessing that because earlier versions only had 20 user checkboxes per table, Checkbox21 and later wont work unless you add the _c.
I’d say it’s a bug that it doesn’t add the _c for fields that start with Number, Character, Checkbox, Date, etc…, when the number exceeds what was built-in to the table in older versions
And since youre adding them and not just using ones carried from E9, you really should give them a more meaningful name than “Checkbox”
You need to remember that the controls on the Epicor Forms are managed by the properties of the Data and Extended UD fields are no different. If the Controls on the Form are Read-Only, it means that the Data has been set to Read-Only. Setting data to Read-Only is typically a function of Logic in the UI and generally follows a couple of patterns.
The Epicor Record you are extending has been set to a Read-Only state - UD Fields on Epicor Records are treated as if the field is a base field so if the Epicor record is set to Read-Only, the UD Fields will be Read-Only. This is usually done when the record is viewed as “Complete”, “Closed”, etc.
The Fields in a Group Box in which you have placed your UD Bound Controls are set to Read-Only. There is an Epicor UI coding pattern where the coder can pass a Container control in to a routine that will then run through all the UI Controls within the container and set the Data fields from the controls EpiBinding to Read-Only (it is the data being set to Read-Only). This is a less common pattern than the first one.
Extended UD Field Naming - Extended UD field names are appended with the “_c” suffix to prevent a collision with Epicor Column names in future versions. That rule applies unless the Extended UD Column uses the same naming convention as the original UD Fields from E9 (base Epicor code will not use that naming convention) so your extended UD Fields names are valid without the “_c” suffix. That said, it really is a good idea to use a name that actual provides a clue as to what you are using the fields for…