I have a scenario where I have an object type that lets end users enter tickets. There have been about 100 tickets submitted and there was a requirement added to allow certain properties in the object type to be visible to ‘owners’. I know I can hid it in workshop but if end users know to go to object explorer the can see the columns and the values. I’ve been trying to use MDO but can’t get it to work when adding new objects.
I created a new backing dataset and the properties that I only want owners to see, I’ve added those properties against the new dataset, dataset B. Dataset A has the properties the end users can see. Dataset B is in a folder visible to only the owners, Dataset A is in a folder visible to all users of the app.
Since there was already existing objects in the object type, I ended up having to just copy the keys from dataset A to a spreadsheet and uploaded it to start dataset B. It seemed to work but when I go to ADD a new object as a end user, it takes and object is added. But then when an owner goes to try and edit the object on the properties in dataset B, it will not save. I am using an action form. It seems like it saves when they click on submit, with no errors, but it does not save.
After some research on the materializations, it appears that when an end user adds the new object, the key is created in dataset A but it does not show in dataset B. So I assume this is why the edits are not working.
Is what I am trying to do possible? is there another way for column restrictions based on permission groups?