In Nintex workflow if you are trying to upload a document by using “Office 365 upload file” and trying to add value in person (user) field. You may encounter the following error “[InputMetaDataXml] : The ‘Fields’ is invalid. Input string was not in a correct format.” The solution is quite simple, you need to map the “User Id” in the “Advanced Lookup” option. Continue reading [InputMetaDataXml] : The 'Fields' is invalid. Input string was not in a correct format.
well i was trying to update the Application ID URI to my appservice url. but it was showing the following error. “Failed to update Application ID URI application property. Error detail: The Application ID URI must be from a verified domain within your organization’s directory.” After looking it closely, i have found that the Home Page URL wasnt been set on the branding option in … Continue reading Failed to update Application ID URI application property. Error detail: The Application ID URI must be from a verified domain within your organization's directory.
Graph API fails to work on Teams in SPFx webpart Just to give you a background, i was working on the SPFx webpart which needs to be available on Teams tab. I was fetching values through Graph API. Though the webpart working well on the SharePoint, but fail to load on the teams. I stumbled to this Git hub discussion, https://github.com/SharePoint/sp-dev-docs/issues/2521 and there was configuration … Continue reading Graph API fails to work on Teams in SPFx webpart
Well with the annoucment of SharePoint Modernization Scanner tool, i thought to give it a try. I ran it for one site collection , which got some data, custom master pages plus some designer workflow. Following are my thoughts about the results sheet i got after running this tool. Page ScanI got useful information, like how many webparts, type of webpart are there on the … Continue reading SharePoint Modernization Scanner, my two cents
So Microsoft graph is a way to go for office 365 API and it’s now depreciating the existing API. But there is nothing to worry about as Graph will take over these API in more enhance manner. The affected API set is the social.following APIs (documentation) – specifically the followed count API (http://<siteCollection>/<site>/_api/social.following/my/followedcount) will no longer return results. I would suggest for all new office 365 solution … Continue reading Updates on SharePoint Online social API
It’s seems that there was an outage in office 365. Received clients calls as well. Updates, seems like still patchy, panic wave for clients and us as well. Continue reading May day, may day, office 365 not working
Just a quick note if you encountered the above error when publishing Nintex workflow. In my case though i have some actions which arent configured properly, but disabled. Nintex will verify the workflow for all the actions when you are publishing the workflow, even those which are disabled. So either removed those actions but put some placeholder/workflow variable to make workflow publish Continue reading Nintex Workflow-Error publishing workflow. The workflow contains action that still must be configured. Please configured all actions and try publishing again.