Forum Discussion
Incremental Refresh Error
Hello,
After setting up incremental refresh based on a date range parameter filter applied to "Modified Date" of a SharePoint Online list, we receive the following error in our Premium Service Refresh History
The JSON DDL request failed with the following error: Failed to save modifications to the server. Error returned: 'Parameter substitution failed with following error: 'Neither mashup nor gateway connection string detected for incremental refresh parameter substitution'. Parameter substitution failed with following error: 'Neither mashup nor gateway connection string detected for incremental refresh parameter substitution'.
Any suggestions?
Thanks!
I get the same error message, and I am too trying to implement incremental reload (as per May release of Power BI).
Honestly, I believe this is a bug as the feature is still in preview.
24 Replies
- xfidelitydjNew Member
Hello,
After setting up incremental refresh based on a date range parameter filter applied to "Modified Date" of a SharePoint Online list, we receive the following error in our Premium Service Refresh History
The JSON DDL request failed with the following error: Failed to save modifications to the server. Error returned: 'Parameter substitution failed with following error: 'Neither mashup nor gateway connection string detected for incremental refresh parameter substitution'. Parameter substitution failed with following error: 'Neither mashup nor gateway connection string detected for incremental refresh parameter substitution'.
Any suggestions?
Thanks!
- AnonymousNot applicable
HI xfidelitydj,
Based on error message, it seems like there are something wrong with your datasource connection and parameters.
I'd like to suggest you to take a look at below link to know more about power bi service parameters:
Using the Power BI Service Parameters to change connection strings (To possibly change between Dev,
Regards,
Xiaoxin Sheng
- gmarroneNew Member
I get the same error message, and I am too trying to implement incremental reload (as per May release of Power BI).
Honestly, I believe this is a bug as the feature is still in preview.
- AnonymousNot applicable
Hi,
I am also facing same issue for Sharepoint dataset.
The Parameters setting is greyed out so cannot test the workaround suggested. It would be good to have a list of what data sources work with incremental refresh.
- AnonymousNot applicable
Same error here using application insights source.
- AnonymousNot applicable
Same error here using application insights source.
- AnonymousNot applicable
Hi
I've been getting same error:
The JSON DDL request failed with the following error: Failed to save modifications to the server. Error returned: 'Too few arguments were passed to the DATESINPERIOD function. The minimum argument count for the function is 4.
Any help would be apprciated
- ElsDAdvocate I
Same error here. My source is an Excel list on Sharepoint.
Normal refresh works fine. I can see the parameters in the Service. So they are set-up well.
After activating the incremental refresh, the service can't find the parameters anymore.
- AnonymousNot applicable
Same error here too. Files in a SharePoint document library. Using the RangeStart and RangeEnd parameters to filter file names to pick up the last n day's files only. The logic works fine when I test it with full refresh and setting the parameters manually. But the same fails with incremental refresh.
- AnonymousNot applicable
This is a little frustrating. I've set up the parameters properly in Power BI Desktop, added a filter to a date/time field with the parameters, set up the table with incremental refresh, and published it into a premium workspace. After all of that, the paramters simply don't show up under the "parameters" section in the Power BI Service.
This then leads to the same error that the original poster is referring to. Does anyone know why aren't the parameters showing up properly in Power BI Service?
- AnonymousNot applicable
The parameters don't show up by design for now. This is a known and documented limitation.
My guess for the why is the handling of the RangeStart and RangeEnd parameters, which has to be automatic for the incremental refresh. Hence they had to disable their management on the UI, because that would lead to confusion. And instead of implementing it in a granular way - which may be underway for the generally available version -, they simply disabled parameters in general.
I really dislike this constraint, because from the end user's point of view it makes no sense, and it imposes a big limit on how one would deal with report development.
- AnonymousNot applicable
So if the parameters are not showing up in the Power BI Service and refreshing the dataset causes an error due to the parameters not being there, does this mean that incremental refresh isn't going to work currently? Is there a work around to this or are we stuck waiting for a more stable release by Microsoft before we can use incremental refresh?
- AnonymousNot applicable
Hi All
I have been getting a different error. Please see below desccription.
My time out limit is set to 5 hours and this returns before the limit is exceeded.
Processing error: The JSON DDL request failed with the following error: Failed to save modifications to the server. Error returned: '{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Unable to connect to the remote server"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} {"error":{"code":"DM_GWPipeline_Gateway_CanceledError","pbi.error":{"code":"DM_GWPipeline_Gateway_CanceledError","parameters":{},"details":[],"exceptionCulprit":1}}} '.. - AnonymousNot applicable
The error description that I catch is "Unable to connect to the remote server". That tells me that you need to dig for the error elsewhere.
- AnonymousNot applicable
Hi
Thanks for reply,
I am currently changing my source from Json to Oracle DB, Will test this out and if it passes will update you.
However when you mean elsewhere do you mean as in where I am fetching the data from source.
Everything is setup accordingly in the desktop.
Also just remembered, My gateway version is 13.0.5780.159, I found this on the Question mark
What I want to know is how recent is this version and also if the versions Desktop & PowerBI aren't current and, will it affect the incremental refresh.
Regards
- AnonymousNot applicable
Hi,
I am pulling data from Salesforce.com and getting the same error.