Dataset Cannot Refresh Due to Duplicate Connection String

[dbabmg]

Hello!

I have a report that has recently hit an odd issue that I am unsure of how to resolve. I have a report that pulls from two different RDS databases and has been working for some time.

Recently I added a second SQL connection in the report connecting to one of the previously mentioned RDS databases. Once published however the data gateway attempts to map the datasources as shown below. 

Everything is green, but with this duplicate present I cannot click apply or select any gateway to use to refresh the report. I am not sure why it is treating the new query as a completely unique source with the exact same connection string?

I have verified the connection strings of the top and bottom sources are exactly the same, pointing to the same database within the RDS instance, and they even autodetect to the same source that is on the gateway, yet they are listed separately.

Any insight into what is going on would be great! I haven't had this issue on any other report over the past year or two.

Thanks everyone!

[mattbitter]

if anyone runs into this again. The solution is to take over the dataset with another user (e.g. your Priv account) then take over the dataset with your normal account again and the issue should be fixed. Not sure how long it will last but it is better than deleting the dataset and re publishing.

[dbabmg]

After some further digging, I have saved my local file under a new name and published it to test if I could replicate the gateway error. This time I received no duplication error and the report could work and be scheduled just fine. 

Is this perhaps a bug? 

[v-lionel-msft]

Hi @dbabmg ,

First of all thank you for sharing your solution, and secondly, I did not reproduce your problem.
What happens if you re-publish the report?

Best regards,
Lionel Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[dbabmg]

Hey @v-lionel-msft ,

Apologies for the delay, republishing changes nothing and still holds the duplicated dataset. But saving the local file under a new name with no changes, and publishing that, "fixes" the problem and doesnt replicate the duplication issue.

However eventually republishing that new copy, spurs the duplication issue again so I haven't gone that route.

Thanks,

Dan