Discussions

We've confirmed that we can successfully create both Registration Options and Program Items via the API by omitting EventFunctionId from the payload.

The remaining issue we're running into is with RelatedFunctions on Registration Options. When we try to link an API-created Program Item to a Registration Option, either via the API or through iMIS Site UI, the connection is silently dropped and does not persist.

To isolate the root cause, I created two structurally identical bare-minimum Program Items, one via the UI (PO8) and one via the API (PO9). The GET response for both items is structurally identical with no differences in any fields. However, PO8 (UI-created) is automatically accepted in RelatedFunctions on both Registration Options, while PO9 (API-created) is silently dropped every time.

This implies the issue is not related to payload structure or missing fields. Something the UI triggers internally upon saving a Program Item is not being triggered by the API, and that missing step appears to be what allows the item to be linked via RelatedFunctions.

Any guidance on the correct workflow for linking an API-created Program Item to a Registration Option would be greatly appreciated.