CB Linked Server for Enterprise Applications.CB Document Metadata Reporting for Salesforce®.Document Extractor – Built for Salesforce platform™.Salesforce Document Management & Integration.SharePoint Enhancements & Blockchain Document Sealing.Digital Transformation – Industrial IoT.CB Exchange Server Sync for Gmail and Google Workspace.Exchange and Office 365 Synchronization & Security.Connect to Dynamics 365 Business Central.Connect to Dynamics 365 Finance and Operations.CB Dynamics 365 Seamless Attachment Extractor.CB Dynamics 365 to SharePoint Permissions Replicator.Dynamics 365 + SharePoint Document Management Suite.Dynamics 365 and CRM Productivity & Access Control.Something has changed in the validation process that is breaking this on Microsoft's side. We tested this same manifest 1-2 weeks ago and it worked fine. They cannot do this now because of the invalid error. We just deployed an update to our add-in today and it requires our customers to update the manifest via the Admin Panel in order to get the latest manifest with Shared Mailbox support. Attempt to install an add-in manifest that has an itemSend configuration defined via the Admin Console "Integrated Apps" page (as recommended in the documentation) (ex.I receive an "Invalid manifest" error (see screenshot) when uploading our manifest that has worked as recently as a week or two ago. I can upload an add-in manifest that contains ItemSend configuration via the Admin Panel. This is an urgent bug that needs to be fixed. I use to be able to upload our manifest, which contains an ItemSend configuration, without any issues (which I should be able to - that's the recommended approach since we can't deploy to the Store).
Just recently, it seems something has changed in the validation of the manifest when deploying an add-in via Admin Panel.
Provide required information needed to triage your issue
0 kommentar(er)
