# A Forms trigger is environment config

A Microsoft Forms trigger breaks the moment you promote the flow, because the form ID is not
portable. Treat the form as two artifacts and the form ID as configuration from the first build.

I had to promote an access-report flow, Form -> Dataverse -> Teams reply, from dev to prd as a
managed solution. The flow hard-coded the form ID in two places: the trigger and the Get response
details action. Moving a form to a group changes its ID. There is no maker role in prd, so nothing
can be fixed by hand.

The fix has three parts. Keep two forms, one for dev and one for prd. Forms has no version control
and every save is live, so a test change would reach production users at once. Put the form ID in a
text environment variable, `report_form_id`, and use it in both fields through Enter custom value.
The variable only appears after you reopen the designer, from inside the solution. Leave the default
empty, so if prd is imported without its own value the flow fails loudly instead of quietly listening
to the dev form.

The prd value goes in the deployment settings file, under EnvironmentVariables with the SchemaName
and Value, next to the connection references. The connections themselves need a functional ID someone
can sign in with, because the Forms and Teams connectors accept user sign-in only and have no service
principal option. That ID needs an M365 licence and must own the prd form, or sit in its owning
group, for the trigger to see it.

A Forms trigger looks static. In an ALM pipeline it is environment-specific config.
