Fabric Ideas just got better! New features, better search, and direct team engagement. Learn more
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.