Find record in automation using current record

Hm, if I were you I'd try:
1. Create a field in the "Updates" table called "Asset record ID"
2. In your prefill URL formula field in "Assets", prefill the new field from step 1 with the Asset record's "record_id()" value

This way the submitted "Updates" record will include the record ID of the record from the Assets table which you clicked the button on, and you can use that record ID for your search

I'm not entirely clear on the use case, but you could also just link them together directly too?

Adam's solution should work, and you can also hide the "Asset Record ID" field in the form since it is for your use only.

To pre-fill form fields, follow this guide: Prefilling a Form via Encoded URL

To hide the "Asset Record ID", use the visibility rule with two conditions, as shown in this screenshot.

If you need help implementing this solution, fell free to schedule a free call with me.

Hi Adam, I pretty much had the tables set up with the Rec ID available and I've now added that Rec ID field to the pre-filled form. But I'm still stymied about how to point to the Rec ID value in the Automation,

Shouldn't I be able to set a condition that refers to that Rec ID value? in the Conditions section above I can only add a string as opposed to a value in a field.

I'm sure I'm missing something fundamental. I do need the Find Record step, right?

@CharlieMullin  you have to dynamically filter the record using the form's "Asset Record ID".

Like this:

I hope this helps! If you need help implementing this solution, feel free to schedule a free call with me.

Totally forgot about selecting Dynamic to present the fields. Thanks for that.

Now I'm getting this error:

Not sure what that means. Asset Rec ID is a short text field, so should be OK. Here are the two relevant fields:

Asset Record ID was submitted via the pre-filled form. Original Asset Rec ID has a formula to fetch its value from a Rollup field that contains the Rec ID from the Assets table. You can see that those values match (the last three records.)

Thoughts?

Sorry I don't see the error in your reply.

Feel free to schedule a free call with me, and we'll make it work.

re: Shouldn't I be able to set a condition that refers to that Rec ID value? in the Conditions section above I can only add a string as opposed to a value in a field.

I'm sure I'm missing something fundamental. I do need the Find Record step, right

Yeap, you need to set a condition to refer to that value and you do need the Find Record step.  In your "Assets", create a formula field called "Record ID" with the formula `record_id()` and use that in your Find Record step.  Specifically, the Find Record step will look for records in "Assets" with a "Record ID" value that matches the value of "Asset Rec ID"

--
As an aside, I'm kind of curious what the formula is for the field "Original Asset Rec ID".  Not related to the stuff I mentioned above mind you, I'm just wondering how you set that bit up

Hey Jsep, here's that missing screensot with the error:

See the Filters error msg at the bottom.

Here's the Original Asset Rec ID properties:

I think Find Records is fine now, but I still have an error in Update Record. Checkout the two screen shots:

Thoughts?

Hm, in the "Update Record" step, instead of using "Original LMSC Rec ID", could you try using "Asset Rec ID" instead?  If that works you won't need the "Find Record" step, sorry about that

Hi Adam, couldn't get that to work either. But it does make sense that I probably don't need the Find Records action.

A record was successfully created in the Updates table, with the correct Rec ID stored in "Access Rec ID". But the "Updated Asset Last Review Date" value in the Updates table was not updated in the "Asset LR Date" in the Assets table.

I think I'll build a simpler model in a separate test base to better see what's going on.

Thanks for your ongoing guidance.

Alright Adam, I have things working now. Really, my tables are glutted and this is such a simple thing to do once I peel away a lot of my unnecessary items. Linking properly between the two tables was key.

Thanks for all your help!