The Content Gate urls generated by the plugin were not encoded. This has been fixed
We've rebranded the icons and publisher names of the models.
By default the new button for adding a document in standard document handling was been removed from the list, for types other than Content Gate or Note. We have added a possibility to overrule this behavior for each type.
Empty or null values in a key where not handled correctly and an error was being throwed. This has been fixed.
In the previous release there was a bug which caused the inter company queries to fail. This has been resolved.
Normally a Content Gate is being resolved by taking the primarydatasource on the form and match it with the data entity which has the same datasource is it's primary datasource as well. In some cases this was not sufficient so we added the possibility to override this by selecting the form and data entity it should use.
It was not possible to use the bulk query feature for intercompany queries. This has been solved.
In some cases an error occurred when Content Gate is configured for the HRM table and a user is signing in to the Production Floor Execution. This error is now being handled silently.
We added to possibility to override the selection of the data entity per form.
When using a fetch xml query the postload method of tables which are being used for linking and not retrieving data is also being called. We have fixed this so this method is no longer called.
The FreeTextInvoiceHeaders data entity had an issue when retrieving the FreeTextNumber field. This has been fixed.
If linenumbers contained decimals the incorrect url was generated. This has been fixed.
The company context was not replaced in the url which caused an invalid url being generated.
If the company context key was another field than the dataAreaId this was causing issues. This has been fixed and now always the dataAreaId field will be used.
The company context was missing in the suggested relations. This has been added.
The field mappings of a relation were not always in the right order (field, related field). This has been fixed.
The previous version did not contain the correct AXTplatform model. It is important to also update the AXTplatform model (provided in this release).
The type of the relation was not determined correctly and therefore the relations where sometimes not shown correctly.
The version number of the Content Gate solution could in some cases not be retrieved. This has been fixed.
Content Gate was not supporting the use of a computed field as a key in the data entity. This has been fixed.
It is now possible to open Content Gate for entities which are in Dataverse and configured as dual write.
We have added the default title field of an entity to the result of the retrieve entity types endpoint.
We have added the display names of the fields in a relation when retrieving the suggested relations between two entities.
In some cases the suggested relations were shown twice. This has been fixed.
The logging in the connector has been extended. Also a guid has been added to the logging form so it is more visible which log lines are belonging to the same request.
When there was no additional authentication set in the Content Gate parameters screen some errors appeared stating no connection could be made. This has been fixed.
Support for expected content including configuration form for expected content rules.
The suggested relation mappings where not calculated correctly. This has been fixed.
When using the compressed view in D365, the CG icon did not line out correctly. This has been fixed.
There was an issue with cross company filtering in the bulk query feature. This has been resolved.
Existing form customizations to enable Content Gate on forms where it is not automatically available where not always working correctly anymore. This was due to a refactoring in the Content Gate Foundation model. This issue is now fixed.
Note that it is advised to re-evaluate your existing Content Gate form customizations. See the examples in the Content Gate documentation at https://docs.content-gate.com/documentation/extendingthecontentgateconnector
For entities with a number in the key the Content Gate url was not correctly created. This has been fixed.
Because of some wrong dll references within the package, the document integration was no longer working. The references have been restored.
IMPORTANT: Because of some wrong dll references in this release it is not recommended to install this version but install the next version. If you already installed this version it is strongly advised to upgrade.
The bulk query feature was not working for entities with a date in the key. This was resulting in a query exception. This issue has been fixed.
In Safari Content Gate was only shown half in the embedded frame. This has been fixed.
When importing documents through data management that are stored in Content Gate, the import failed with a manifest error (missing mime type). This issue has been fixed.
The content category that was used when uploading a document to Content Gate was defined in the parameters. This means the same category was used for all documents. To provide more flexibility in selecting the content category, the category can now be defined on the document type. When uploading a document for a specific document type, the content category defined on the document type will be used for uploading the document. If no category is defined on the document type, the document type from the parameters is used.
Content Gate is enabled in all legal entities by default and there was no option to disable the functionality in one or more companies. This option now has been added. In the Content Gate parameters it is possible to disable the functionality for one or more legal entities. In legal entities where Content Gate is disabled the Content Gate button will not be available on forms.
We've added functionality to Content Gate for querying Dynamics more efficient. To support this functionality a data service has been added.
The embedded view was not working correctly in Edge. This has been fixed.
The Content Gate button was disabled for records in tables with Valid Time State enabled that were not valid on the current date. This issue has been solved.
AXtension® Content Gate is now loaded within an object instead of an iframe, which should load quicker.
When using Internet Explorer, Content Gate was only shown half.
As of now the Content Gate icon is only visible for users with the AXTcg_User role. Opening Content Gate was previously assigned to the System user role, to make it possible to restrict access in a better way this was changed.
The color if the icon has been changed to blue, according the style of the latest platform update.
No bugfixes in this release.
IMPORTANT: after installing this package, reconnect from Content Gate.
A plugin is developed for using Content Gate as a storage location for D365 document management. On document types Content Gate can be chosen as the storage location. For D365 entities that are configured in Content Gate documents can be uploaded, deleted and viewed directly from and to Content Gate.
When debugging issues it often happens that a production database is restored to the ACC environment. This causes the ACC environment to be linked to PROD content gate instead of Sandbox. In order to fix this the user has to reconnect the Sandbox environment by hitting connect on the business entity provider. To prevent loss of data now the connector validates if a user is coming from the same url as configured in the business entity connector.
In Safari the embedded view was loaded in a very narrow container. This has been fixed.
The caption of the close button in the embedded Content Gate view was not clear. it has been changed to "Close documents".