While scheduling refresh in Power BI, you might get below error . Issue: Unable to convert the value '<pii></pii>' from the source data type 'VT_BSTR' to the expected data type 'VT_I8 . Cause/Reason Behind: Column datatype mismatch between power bi desktop and power bi cloud report. Solution: Edit query in power bi desktop and change the data type so it’s in sync with Power BI service/cloud. Example: In my case, I have modified a column’s datatype from decimal to whole number (to display no. of days). Now power bi desktop and power bi service synced up and I could perform automatic data refresh.
Today's Issue: Volatile function error for SharePoint calculated field current date While creating calculated column to find date difference, I encountered this error. Here I have provided the resolution to fix it, Create a new column called Today (Single line of text). Create a calculated column , name it anything you want, say ' CurrentDate '. In the formula , insert the column you created previously ' Today '. Set the data type to ' Date and Time '. Set the Date and Time format to ' Date Only '. You can even select Date & Time if you would want to use hours/minutes as well. Now delete the ' Today ' column you created in first step. Don't worry, just go ahead. Add the 'CurrentDate' column to your view and check the value. You should see today's date in there. Modify the formula as required, you can use the column Today just like the function [Today] without any issues. Same approach could also be used for [Me],...
One of my SP 2016 application is using SPDActivities of Email extended feature of DP.SharePoint.Workflow to provide custom "From" address. But customers started to complain that they are not getting reminder emails anymore. Find below my STAR analysis, Situation : Recently I was facing an issue - Approval workflow failed to run. Customers not getting reminder emails anymore. Task : - Planned to look into SharePoint services, IIS site, web.config files (WFE and App Server), Latest patch/MS update/CU, Users permission. Analysis : Started looking into each below items, - SharePoint Timer Service and Administration services were running and good - Account which is running the workflow got required permission - DP.SharePoint.Workflow got activated for the web application - Checked into web.config file in WFE server and App Server for below sections Under <SafeControls> below 3 lines need to added both in WFE and App server web.config files, ...
Comments
Post a Comment