Recently for one of our plugins, that moves attachments to the Azure Blob Storage, we got the below exception. BlobFileName: WFU000069107_Inside Install – CFC__2024_03_03_12_24_05_179_temp.jpgCaught Exception: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding…
Continue Reading Nishant Rana’s Article on their blog
Fixed – The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters exception in Plugin (Dataverse / Dynamics 365)
Recently for one of our plugins, that moves attachments to the Azure Blob Storage, we got the below exception. BlobFileName: WFU000069107_Inside Install – CFC__2024_03_03_12_24_05_179_temp.jpgCaught Exception: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.System.FormatException: The input…
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
- Dyn365CE7 May 2024Use Filter Array action to remove values from an array variable – Power Automate
- Dyn365CE6 May 2024Fixed – The latitude or longitude for the User record associated with this resource is invalid – Dynamics 365 Field Service /Dataverse
- Dyn365CE30 April 2024Use Geolocation Settings for Location Tracking and Auditing – Dynamics 365 Field Service
- Dyn365CE29 April 2024Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)