Dynamic Form Rule - Adding Record in Related Sub Table

Xavier:

Totally makes sense.   I am just having trouble with "Add a Record."  I am not seeing this option in drop down.  Any ideas?

Thank you,

Dirk

Note that I was suggesting using Automations, NOT Dynamic Form Rules.

You can access Automations by going to settings, and then Automations -> New Automation.

Form rules cannot add a new record - so that would not be suitable for this.

Xavier:

Simple Automation seems easy enough.

I am having trouble adding a record in a related table (I'm pretty certain).
Passing record ID or something like that.

Dirk

Assuming that your relationship is as follows:

Parent Table:  Work Orders
Child Table:  Receivables

1 Work Order has many Receivables

Then when you have the Action in your Automation for "Add a Receivable Record", you would want the [Related Work Order] to be [Record ID#] from the Trigger Work Order.

For example - if one of your trigger conditions is that in a Work Order, [Status] = "Complete", then now the fields in that Trigger Work Order are available for you to use in the Automation.

So you would want the [Record ID#] for that Trigger Work Order to be the parent of your new Receivables record (by specifying that as the value for your [Related Work Order]).

I'm close.... I'm actually not using Record ID#.  I am using [Work Order Number] and [Related Work or Number] in sub table.
_

When you view that relationship (between Work Order and Receivables), what is the "Reference Field"?

That's what you should be specifying for the parent Work Order.

By default - the Key field in Work Order (or any table) is [Record ID#], and the default Reference field would be something like [Related Work Order].  That's why normally you would fill in [Record ID#] into [Related Work Order] for the new Receivables record.

If you're using other Key fields (or Reference fields) - you would adjust accordingly.

Xavier.... im getting old.  More an issue of focus and attention to detail.

Appreciate all your help.  Just got Automation to function as desired!

Regards,

Dirk
_

Great to hear! =)

One last question:

Can you sort of do the reverse?

If the Related Procurement Table has a zero value for an item purchased, can you select [Do not invoice] checkbox on [Parent Work] Order Table?

Yes - as long as there is a valid Triggering condition, and trigger record knows the reference field for the parent work Order.

So for example - if you add / modify an Procurement Line Item record, with a [Value] = 0, then as long as you have the reference field back up to the Parent Work Order record, you can do the same thing.

i.e. Have an automation check the [Do Not Invoice] checkbox on the parent Work Order.