- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2015 11:14 AM
Originally, I thought this was impossible..
However, it was implied that my belief was incorrect and I was even Demoed a case where this can work.
Now, when trying to make this happen, I'm at a loss.
Example. Say I have a reference field to an asset, and I have another dot-walked field on this form that displays the asset's assigned_to.
I want to be able to change the assigned_to directly from that form. It's writable on the asset, but readonly on this form.
Is this possible? What am I missing?
Thanks,
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2015 11:39 AM
Stephen,
Also, if the field 'Asset' on the form is readonly may be using the dictionary 'Read Only', then the derived fields from that reference will also be readonly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2015 11:42 AM
That's it exactly. However, I do need to ensure that the asset cannot be changed, just the listed attributes of the asset.. Playing with UI policies for that one..

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2015 11:49 AM
Hi Stephen,
In that case the field should be read only on the asset table. But you mentioned that you were still able to change on the asset table. Not sure how that worked.
Can you please confirm if you were able to write on asset table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2015 01:33 PM
Sorry, I was unclear.
On MyForm, I want to display a readonly field for asset. I want to display a writable field for asset.assigned_to. Asset.assigned_to wasn't editable because the asset field was readonly in the myform dictionary. I changed it so that it was writable in the dictionary, exposing the assigned_to, then used a UI policy to make the asset field read-only again. As I was hoping, the UI policy didn't create the same problem for it's dotwalked fields as the dictionary setting.
Worked like a charm.
Thanks,
-Stephen

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2015 04:34 PM
Thanks Stephen for the update. Its now clear