Skip to main content
Question

Snapshot Update

  • August 6, 2019
  • 0 replies
  • 90 views
I have 2 tables - Table A and Table B - that are related.
In the records in Table B I have a field - Field A - that is a lookup field back to Table A.
I also have a field in Table B - Field B - that is a snapshot of Field A.

The logic is if a user does not have permission to view the related record from Table A then Field B is displayed on the forms for Table B. If they do have permission they will see Field A.

The issue I have is that if someone edits Field A in Table A naturally the snapshot field, Field B in Table B, is not updating given its nature. To update I need to review an exception report and manually update Field B by re initializing the field for existing records.

I am wondering if there is possibly a solution to this that I am missing? Could I 'trigger' an update of Field B somehow through a table-to-table import or something different? I am thinking not however would be keen to hear before tackling a possible rebuild of my architecture.

Thanks,
    This topic has been closed for replies.

    It sounds like you are doing this to solve a Permissions issue.

    How about if when the Table B Record is Saved, you trigger an Automation to Copy the lookup field into a scalar mirror field.

    But then as you point out, you need that scalar field updated if it�s lookup value changes due to an Edit if the Parent record. You can also use an Automation to trigger a saved table to table import, merging Table B into itself and mapping the lookup field into the scalar field. The saved table to table import will be filtered where the lookup field is not equal to the scalar field.
    Terms & ConditionsAccessibility statement