You’re offline. This is a read only version of the page.
105
I have a user that wants to add 7 additional custom fields to the asset card, but I am concerned of what the impact would be with MS updates as well as other departments that don't have a need for these fields. My initial thought was to use the provided field (Engine) and document all of the details in a open text field, the ask if for separate fields to be able to run reports. Has anyone had any experience with this type of situation?
Have you considered asset properties? docs.microsoft.com/.../asset-properties You will not see them directly of the asset card, but they would be perfect for your use case without any changes to the data model. And all property readings land in a flat table "Property Log" so that you can create reports.
Of course you can also add them to the asset table and have 2 separate forms or 1 form with some show/hide conditions. If you follow the design guidelines, there shouldn't be a problem with upgrades, however at least some testing will always be helpful.
Decision depends on the requirements around these 7 fields. Logic is easier to implement with approach #2, but if you add fields upon every single user request it will be hard to manage at the end...
Share
Report
All responses (
Answers (
