The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
Hi, I've gone in to make a change to a dataflow in the service today and have started to received a configuration error and gateway is missing (displaying as none). This is despite the refresh occurring without issue and I'm also able to create a new dataflow with the gateway connection for the ODC I'm using. Any thoughts on what might be happening?
Thanks
Solved! Go to Solution.
did you by any chance change the spelling of your dsn ? Since about June 2020 the gateway connection definitions are case sensitive. If you have multiple data sources with the same connection but different case the result will be "no gateway available" and the available gateway being shown but not selectable, with duplicate connections.
To mitigate you need to correct the spelling discrepancy and then re-publish everything.
did you by any chance change the spelling of your dsn ? Since about June 2020 the gateway connection definitions are case sensitive. If you have multiple data sources with the same connection but different case the result will be "no gateway available" and the available gateway being shown but not selectable, with duplicate connections.
To mitigate you need to correct the spelling discrepancy and then re-publish everything.
Hi @lbendlin , I didn't but this is exactly the issue as you described. The connection in my data model is in uppercase but there is a lowercase connection string appearing in my datasources under gateway connection tab. I can't figure how this is happening as I have no lower case connection strings anywhere in the model or in the gateway dsn. It could well be that I'll have to recreate to dataflow to resolve. Thank you for getting back to me. 🙂