Select to view content in your preferred language

Re-calculate annual next inspection dates in a Repeat table

380
2
11-01-2024 06:13 AM
neomapper
Frequent Contributor

Hello all,

I am putting together an inspection workflow that will allow our company to inspect preloaded compliance assets, along with the first set of records in the inspection table, but I'm having issues getting the next compliance date in the repeat to calculate the next annual year when someone creates a new inspection record. I will provide the .xlsx below if someone is able to help. 

Note - We are using the survey123 inbox to pull all the inspections on the devices.

Thank you,

Jordan

neomapper_0-1730466428913.png

 

0 Kudos
2 Replies
abureaux
MVP Frequent Contributor

Could you please elaborate? I don't see any calculates in your repeat. And your calculates in the main table appear to be working as intended.

And just a tip as it isn't immediately obvious. But Groups and Repeats don't like Hints. You can drop that text into a note field to get it to show.

ChristopherCounsell
MVP Regular Contributor

Don't copy paste in Excel. Paste values only. Those green triangles in your label field show you've pasted in and overwritten formatting and it's throwing data validation warnings. You shouldn't get these in the label column, and inversely you might override valid warnings elsewhere.

You are leaving yourself prone to logic loops as well as users editing previous inspections. We've done similar workflows with inbox. Limit repeats to adds, repeat count of 1, and calculate the parent based on the new repeat entry.

However at some point you hit issues with wanting to use values in current state (next inspection) whilst also calculating future state (next inspection).

It's much easier to use Field Maps to show the asset and inspection history, a custom url to open the survey (inspections table only) and pass data in (inspection dates), then post process to update the asset e.g. fme, python, if required.

We might be able to help you achieve your calculations if you share more details but at a glance it looks like you'll hit loop or calculation issues...