Microsoft Dynamics 365
on 5/20/2019 4:19:59 PM
Thank you for your suggestion. To help us in our review process, we’re requesting votes from the community to help us understand the importance of this functionality. This posting is provided “as is” with no warranties, and confers no rights.
Our customer is also waiting for this functionality to become available.
After raising this as an error today I was informed there was an idea available, unfortunately this idea has been initiated almost two years ago.
I have raised this as an error through LCS 6 weeks ago, but has been informed today that it is by design and that I should go add a comment to this idea. So here goes:
To my customer it is not important to have the custom field included in the position action form. But for other customers - and other custom fields - there could definitely be a scenario for this.
Under all circumstances: even when enabling personnel actions, it must still be possible for HR to maintain the value in a custom field. If not directly in the positions form, then at least through Change timeline > Manage changes. Where you can add the custom field, but it remains not-editable. No matter if personnel actions are enabled or not!
Which is definitely an error in my opinion, but Microsoft support says no. It is by design.
As it is now, we have a situation - as personnel actions are enabled with the customer - where their custom field is useless because it cannot be edited.
This could be strengthen by being able to specify which fields are mandatory to complete