Loading...

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)

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 … Continue reading "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)"

Published on:

Learn more
Nishant Rana's Weblog – Everything related to Microsoft .NET Technology
Nishant Rana's Weblog – Everything related to Microsoft .NET Technology

Everything related to Microsoft .NET Technology

Share post:

Related posts

SQL4CDS UTC Mode: Converting Advanced Find Date Filters to UTC Boundaries– A Quick Reference (Dataverse / Dynamics 365)

While validating record counts for a Work Orders view in Dynamics 365 Field Service, we ran into the same underlying issue covered in an earli...

7 days ago

Hide Expired Sessions in Event Registration Form using JavaScript (Dynamics 365 Customer Insights – Journeys)

One of our recent requirements was to ensure that users could no longer register for event sessions once the session had already ended. The go...

8 days ago

When Entity.Id Is Guid.Empty with QueryExpression.Distinct = True (Dataverse)

While optimising the performance of a Dataverse plugin, we noticed a QueryExpression using ColumnSet(true). The business logic only required a...

14 days ago

Implementing Cloudflare Turnstile for Dynamics 365 Customer Insights – Journeys Real-Time Marketing Forms

Check the previous posts for more details – In one of our recent projects, we implemented Cloudflare Turnstile (Invisible) for a Dynamic...

15 days ago

Custom Form Submission Validation in Dynamics 365 Customer Insights – Journeys: Inside the Validation Pipeline and the “ms_captcha_solution” Error

While implementing custom form submission validation (server side validation) for Dynamics 365 Customer Insights – Journeys Real-Time Ma...

21 days ago

Implementing Server-Side Honeypot Validation for Dynamics 365 Customer Insights – Journeys Forms

In our previous post, we implemented a simple Honeypot for Dynamics 365 Customer Insights – Journeys Real-Time Marketing forms using Jav...

22 days ago

Implementing a Simple Honeypot in Dynamics 365 Customer Insights – Journeys Real-time Marketing Forms

While working with Dynamics 365 Customer Insights – Journeys Real-time Marketing Forms, we wanted to explore a simple way of reducing bo...

1 month ago

Retrieve All One-to-Many Relationships and Cascade Delete Behavior for a Dataverse Table Using C#

While working on a Dynamics 365 Field Service cleanup, we needed to delete a large number of Work Order records. Before doing so, we wanted to...

1 month ago

Why SQL4CDS Record Counts May Not Match Advanced Find for Date Filters (Dataverse / Dynamics 365)

While validating some Dynamics 365 Field Service data recently, we came across an interesting scenario where SQL4CDS and Advanced Find returne...

1 month ago

How We Successfully Removed the Resco Woodford Managed Solution from Dynamics 365 Field Service

Recently, we needed to remove the legacy Resco MobileCRM (Woodford) managed solution from a Dynamics 365 Field Service environment. Although t...

1 month ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy