8I'm trying to build a Power Automate cloud flow that triggers when a purchase requisition in D365 Finance is approved. Following the admin reference for virtual entities has got the Dataverse table visible, and the trigger seems reasonably intuitive with a requisition status Closed, but when attempting to test the flow, the trigger actions reports the error below
Exception parsing mserp_requisitionstatus eq 'Closed' submitted for attribute filterexpression of callback registration. Target entity: mserp_purchaserequisitionheaderv2entity. Exception: System.InvalidOperationException: The entity 'PurchaseRequisitionHeaderV2Entity' does not have a key defined
The design view of the entity shows that it does have a key:
However, this doesn't show up in the Dataverse table:
I've read about guids being desirable keys for data entities, but it seems strange that it would be necessary to extend a standard entity with a key like this to get it to show in Dataverse (to be useful, I'm thinking it would need persisting in the database, which would be a big enough change to feel very unlikely). Anyone please able to suggest some step I may have missed in the virtual entity addition to Dataverse that means keys haven't been created?
