Closed souvik221 closed 1 year ago
Could you please share the complete debug log?
Hi @maikvandergaag ,
Good day !
Could you please have a look on the release log that has been shared above ?
Thank you in advance.
I will have a few days off at the moment
Hi @maikvandergaag,
Can I expect an update on this issue now ?
-Souvik
Publishing a new version at the moment could you try with that version?
Hi @maikvandergaag ,
I still don't see the new version at the moment in my ADO org.
Deployment will be done automatically because it is still version 5
The statement "Publishing a new version at the moment could you try with that version?" is not clear at all . What do you exactly mean ??
I published a new version of the extension with a small adjustment please try again
Still getting same error as below :
Coudl you please share the complete logs again?
Hi @maikvandergaag ,
Any findings on the above detailed logs ? Please suggest.
-Souvik
Hi @maikvandergaag,
Any update on this issue which is pending since long. Do you need more time to fix this ? please suggest.
I will need more time. Please check on your end if you are able to deploy the report with the PowerShell module from Microsoft
Any update on the fix @maikvandergaag ?
No not yet I'm working on it and also have a day job. Did you try with the powershellmodule
refresh schedule is working using PBI powershell cmdlets.
refresh schedule is working using PBI powershell cmdlets.
@souvik221 can you please share your powershell code where you set the schedule?
I'm running into the exact same problem, but the strange thing is that for 1 dataset it works perfectly and within the same workspace, with the same authorisations another dataset gives the same error. The only difference is the name of the datamodel.
@souvik221: Would be great if you can share your code you used.
I think I solved it, for myself at least. The customer had manually set the schedule and with automating the deployment via pipelines I ran into this problem. They also set the notification via e-mail on, I didn't change this setting in the body of the call ( only '{"value":{"enabled":"false"}}'). I found this article https://www.linkedin.com/pulse/automating-power-bi-deployments-himanshu-khanna/?trk=articles_directory where he points out two lacks of the API on the scheduled refresh:
Tip: Currently API doesn't respond well to two parameters: TimeZone other than UTC notifyOption other than NoNotification
I added those params in the body and the schedule update went well again for my dataset.
If I look it up in the documentation it actually points the notification only supports no notifications https://docs.microsoft.com/en-us/rest/api/power-bi/datasets/update-refresh-schedule "Service principals only support the NoNotification value."
Now the other calls without the parameters of timezone and notification also work ('{"value":{"enabled":"false"}}') for my dataset. I apparently couldn't handle the settings, even if you don't update them in the call.
@souvik221 maybe you can check the timezone and notification settings on the dataset.
And I'm still very curious about the powershell code :) because obviously you want a notification when the refresh fails.
@souvik221 are you able to share the code you used?
Hi @maikvandergaag
Hope you are doing great !
set refresh schedule job failing in power bi actions extension in ADO. Detail debug log below
Rest all jobs as mentioned in below snapshot are working fine with no errors !