I have a "Documents" listing page which is an EntityList showing records from a Document entity and filtered to show records for the currently logged in portal user.
I also have a mechanism whereby the user can submit new documents. There are a large number of different document types that can be created so what we have done is separated out the actual content for each document type into separate entities (rather than having a massive number of fields covering all document types in the Document entity).
So for example if the user submits a document of type "Expenses" what will actually happen is that there will be an Expenses entity record created which will contain the detail of the expense document and then in a plugin off the creation of the Expenses record, a "Document" entity record is created which will have a lookup to the relevant "Expenses" entity record.
This has been implemented as an entity form against the Expenses entity (and the plugin fires to create the Document entity record).
The problem with this is that my "Documents" listing page does not show the newly added expenses document straight away. I have to restart the portal for it to appear. I'm guessing this is because the entity form is defined against the expenses entity rather than the document entity (it has to work this way as the fields exist in the expenses entity).
I have tested using an entity form against the "Document" entity and the list updated straight away. This is not practical though as there are thousands of fields across all of the possible document types.
Anybody know of a way to force the entity list to show updated data on the form entity where records are created via a plugin (and not directly via the entity list)??
*This post is locked for comments
I have the same question (0)If this is for Dynamics 365 portals or CRM portals and not Adxstudio then you need to ensure that the entities your documents and plugins touch have the Change Tracking enabled. If Change Tracking is not enabled that cache invalidation messages will not be sent to the portal.