Push updates in both directions with record links
under review
C
CKISS Fulcrum Manager
Please allow the capability to update fields that are the same (dependent) in all apps with record links from both directions, including after a record link has been created. For example: site pin with site details. A record link to survey details for that site. When info in the site details is updated, the survey is not updated with that information as the survey has already been created. If the there are spelling mistakes or errors in the fields in the site details, these changes can be fixed however these changes will not carry over to the surveys. The surveys will have whatever errors were present when the record link was created. There is no possibility to update the data after the link has been created unless you manually do it... which is time consuming and can result in errors.
This causes a nightmare of data issues as changes can be made in the survey and not show up in the site or vice versa.
Being able to push changes forwards and backwards through record links should be a possibility. Please make this work! My data is getting so messy and makes me consider not using records links.
Stephen E. Van Hoose, RA
We’re dealing with the same issues as other commenters, spending a lot of time updating data events to push data updates in both directions when record data is changed. It will save a lot of time on our end having to copy a and test a data event that pushes the data updates correctly. We built one today to update the geometry of one app when the geometry is updated in the record link.
Katie Briggs
under review
Shawn Pickett
I agree, I have been using data events and local storage to manage this data, but it is time consuming to set up and fraught with issues if something goes wrong with the code.
Samuel Sikes
I have not seen any update on this, and there REALLY needs to be. There is now official documentation (https://help.fulcrumapp.com/en/articles/1710389-is-there-a-limit-on-how-many-fields-an-app-can-have#:~:text=The%20apps%20that%20you%20build,can%20add%20to%20your%20app.) suggesting "you can work around" the issues caused by large apps by "leveraging record link fields.." This is bad advice if cascade updates, creates, and deletes have not been added; since you can run into orphaned linked records, linked records in different states than their parent record, etc.
Samuel Sikes
I just got done chatting w/ Fulcrum support about this. The ability to cascade update all records affected by a linked-record update is necessary. Forcing the end user to use the Fulcrum API w/ web-hooks to perform cascade updates isn't a good solution. This is something that should come standard in the base product. With this ability, the record-link feature would be fully formed.