Power Platform Community Forum Thread Details

I am wanting to create a automation that triggers when a record is created in one table and creates multiple records in a different table. The desired outcome is to have 12 records (one for each month in the year) created in the Financial Forecast table when a new record is added to the Initiative table. The new records should have values set for: Financial Forecast Month, Financial Forecast type, and Initiative (and this should correspond to the initiative created in the trigger). I have created the following flow (see IMG 1 for detail):
When a Row is added to the Initiative
Initialize StartDate
                Type: String
                Value: [blank]
Initialize NewDate
                Type: String
                Value: 2025-01-01T08:00:01
Apply to Each
                Output: addmonths(variables('StartDate'),1)
                Add a new Forecast Record
                                Table name: Financial Forecast
                                Financial_Forecast_ID: [SEEKING INPUT]
Financial Forecast Month: Variable(‘NewDate’)
Financial Forecast Type: Forecast
Initiatives (initiatives): Set Name(initiative)
I have placed the Add a new row action within the loop. When I try to save the flow I receive the error message that the 'Financial_Forecast_ID' is required. Aren’t the record ID fields populated automatically? I am unclear what the input should be here.
IMG 1

Categories:

Building Power Apps

@JHat1121 Hi,

If you are using Dataverse, when creating new records, you do not need to supply the GUID ID manually unless:
You have a custom ID field that is required
Or you're using alternate keys for deduplication
So, if Financial_Forecast_ID is not the internal GUID/primary key, but a custom required field, you must populate it.

Suggestion:

Option 1: Remove the ID if it's not needed
If Financial_Forecast_ID is not really needed, go into your Dataverse schema and:

Mark it as not required

Or remove it from the form/data model if unused

Then the flow can create records with the system-assigned GUID.

Option 2: Auto-generate a value
If the field is required, and must be populated (e.g., for integration or reporting), then you can:

Inside the loop, use a unique identifier expression, for example: