I am working with Microsoft on a support case. The support case came up because a lot of inconsistent and buggy behaviors that we were noticing in relation to dataflows. We are trying to build automated deployments from git via the "IMPORTS" API:
https://learn.microsoft.com/en-us/rest/api/power-bi/imports
With datasets we are able to import and update our assets pretty easily.
Whereas with dataflows, the use of the "IMPORTS" API is hit-and-miss. Things work sometimes and then fail others. There isn't any rhyme or reason to it, despite the fact that customers have sunk a ton of time trying to make it work. See links:
After getting a month into this support case , Microsoft is starting to say that using the REST API to import changes/updates in dataflows is unsupported. They say the REST API as a whole is supported, but certain use-cases are arbitrarily unsupported (ie. updating an existing dataflow might work in practice, as a matter of coincidence/chance.... but they say it is not a "supported" operation, so they don't want customers to report the related bugs.).
It would be one thing if I was doing something very unusual, but every customer would expect to use this REST API to serve this purpose. Every customer would expect the dataflow operations to behave in a way that is similar to the dataset operations, for the sake of uploading new assets and updating existing ones. In fact there are already lots of customers using it like this (see links above).
Has anyone else encountered pitfalls where they use a REST api, where it won't work, but Microsoft arbitrarily says its "unsupported"? Have you ever seen documentation that calls out "supported" and "unsupported" modes of using a REST API?
