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 moreRelated posts
Power Platform – Information regarding the deprecation of the Microsoft Graph Security connector
As of April 29, 2026, the Microsoft Graph Security connector has been deprecated and is no longer supported. This follows the deprecation of t...
Power Platform | Empty “Unresolved References” in Solution Import
While deploying a managed solution to a target environment, it failed with this error: No component names. No helpful details. Just empty quot...
Microsoft Copilot in Dynamics 365 Customer Engagement: Where Teams See the Most Value
Artificial intelligence, particularly Microsoft Copilot in Dynamics 365 Customer Engagement, is quickly becoming part of everyday work across ...
Microsoft 365 & Power Platform Call (Microsoft Speakers) – April 28th, 2026 – Screenshot Summary
Call Highlights SharePoint Quicklinks: Primary PnP Website: https://aka.ms/m365pnp Documentation & Guidance SharePoint Dev Videos Issues...
Power Platform – PayGo not required with Self-Service Disaster Recovery (SSDR)
Starting May 22, 2026, Pay-As-You-Go (PayGo) is no longer a mandatory requirement to enable Self-Service Disaster Recovery (SSDR) in your prod...
Excel Desktop update required to connect to Power Platform Analytical Dataflows
Excel Desktop must be updated to Build 16.0.17932.20732 or newer by May 27, 2026, to maintain connectivity with Power Platform Analytical Data...
Practical AI in the Power Platform
Practical AI in the Power Platform has quickly become one of my favorite sessions to deliver this year. It’s the perfect blend of “what’s poss...
Power Platform Pay-As-You-Go Explained: Pricing, Benefits, & Use Cases
In the current digital environment, businesses need operational flexibility by using software tools to enable automation and improve data anal...
Power Platform – Managed personal developer environments are now included in inactivity-based cleanup
We are introducing an automated process to delete inactive personal developer environments, starting April 24, 2026. Personal developer enviro...