i have changed / added / renamed fields in some tables. i have checked the views which use those tables, and have ensured that the changes are reflected in the view (e.g. ensured that 'include all fields' is checked).
however, whenever i use a VIEW for a datapage, the 'datasource' fields that are available for record-level security or for lookup tables in dropdown elements show only the old fields and the old field names. the only way to see the correct fields is to use the table as the datasource, but of course that shouldn't be the case.
all this is to say, it seems that dropdowns in datapages for lookup tables and record -level security are using cached versions of the original view/table.
a screenshot is tough to pull off, but perhaps this example will help:
current table fields:
field ABC (originally named field AB)
field XYZ (not originally in table or view)
current view fields (match table, as expected):
field ABC
field XYZ
fields available for dropdowns and record-level security in datapages (does not match table; unexpected behavior):
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
aaronfreed
i have changed / added / renamed fields in some tables. i have checked the views which use those tables, and have ensured that the changes are reflected in the view (e.g. ensured that 'include all fields' is checked).
however, whenever i use a VIEW for a datapage, the 'datasource' fields that are available for record-level security or for lookup tables in dropdown elements show only the old fields and the old field names. the only way to see the correct fields is to use the table as the datasource, but of course that shouldn't be the case.
all this is to say, it seems that dropdowns in datapages for lookup tables and record -level security are using cached versions of the original view/table.
a screenshot is tough to pull off, but perhaps this example will help:
current table fields:
field ABC (originally named field AB)
field XYZ (not originally in table or view)
current view fields (match table, as expected):
field ABC
field XYZ
fields available for dropdowns and record-level security in datapages (does not match table; unexpected behavior):
field AB (not field ABC, and not field XYZ)
improved clarity
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.