After a semantic model has been set up with a refresh schedule, that information is not passed to Git Integration if that fabric item is synced to a Git Branch/Repo. Ideally, if a refresh schedule is changed, it would be great if that is saved on the model itself, so that if that same model is pushed to another workspace through APIs or other deployment options the schedule will pass along with it. Currently, there needs to be a seperate RefreshSchedule API call which adds more steps to a deployment process when these have already been set previously.
on:
Customers should ereceive notifications for all th...
miguel
on:
Recent Data and Recent Connections
on:
Need more details on Average utilization% in Capac...
lbendlin
on:
Increase the 1,000 Item Limit per Fabric Workspace