Here you can find an overview of all planned features and user stories for COSMO Data Integration Framework. Visit this side frequently to stay up-to-date with planned features and availability. All information is subject to change.
The planned availability is an estimation, only. Also the order might be changed on new influences.
|Feature / User Story||Planned availability|
|AL Interfaces for Communication||Q3/2021|
|Repository Type SharePoint||Q3/2021|
|Compression of Communication Type Web Service||Q4/2021|
|AL Interfaces for Repositories||Q4/2021|
|REST Communication Messages||2022|
Please contact email@example.com for further information.
AL Interfaces for Communication
The message communication of COSMO Data Integration Framework allows only extensibility by events, currently. The AL interfaces introduced with Business Central v16.x enable to create much better extensibility to send and receive partner message, and manage repository handling for messages.
Repository Type SharePoint
The former C/AL version of COSMO Data Integration Framework was able to communicate with a Microsoft SharePoint, easily. It was possible to write and read data from SharePoint lists like any other table. This features will be redeveloped using the technology OData API of SharePoint, instead of SOAP API.
Compression of Communication Type Web Service
In SaaS environments, the messages are mostly send by partner communication type
Web Service to another database. The XML message used as communication contains full textual content and can become large in data size. Compressing the messages will make the data payload much smaller and therefore send the messages faster.
AL Interfaces for Repositories
The repositories can only be extended by events, currently. The AL interfaces introduced with Business Central v16.x enable to create much better extensibility for custom repository types. Depending on the concept, the line actions might be also moved to interface technology.
REST Communication Messages
As COSMO Data Integration Framework can create and read JSON repositories, the app should be able to directly communicate with REST APIs. The request and response for OData must be managed in a total new message handling, to allow concatenating of mapping execution.
Senden Sie Feedback für. (Beachten Sie, dass diese Umfrage auf Englisch ist.)