Form Personalisation Issue

A client wanted to add a new field to the sales line table, which would be a lookup to a new table. This is not an unusual request, so should don’t have been a problem. The client wanted, however, to not have the field shown no the sales form, and that couple of users that needed this field would personalise the form to add the field to the lines grid. This is where things got interesting.

The client is using Dynamics AX 2012 R2 with CU7. During the testing cycle, the user could add the field to the form, but the field was read-only and not editable.

To check the code has been completed correctly, the field was added to the form. This resulted in the field working correctly. Also tried adding the field via personalisation, with the field already on the form, and both fields worked fine. So the field only didn’t work if the field was only present on a personalisation. Having never seen this before, wonder if this was a bug, so did some more testing.

A new form was created, added the purchase table, and a grid. Added the field perched and purchstatus to the grid. Opening the new form, a personalisation was added to include the payment method. This is a standard system field, so eliminates any development issues related to relationships. The new form had the same issue. The field was not editable, the lookup would not display. If the field was added to the form, then the personalisation added, it worked fine.

Since CU7 is not the latest version, I created the same test in CU9, with the latest version of the kernel. This produced exactly the same result.

Curiosity kick in now, so I tried the same test on AX2009, AX2012R3 and D365F&SCM. The system worked as expected in AX2009 and D365F&SCM, but had the same issue in AX2012R3.

If AX2012R2 or R3 is giving you difficulty with making personalisations to forms, you’ll need to add the field to the form and not use personalisations.