Data Source change from database A to Database B with same schema fails

[oldwoman]

We changed our database location.  Same schema but different schema name different location and credentials.   We modified the data source and credentials.  Some tables come through no problem so I know the connection to database is good.  We changed the schema name for each table.  We have selected to include relationship columns, but these are not coming through.  Specifically the navigation step would have additional relationship columns, but now these are not showing up.  If I go to the navigation step and select the cog ("settings"), I see the tables I needed to include.  I checked the native query for the working report pointing to database A and the not working report pointing to database b.  The native query is exactly the same.   The M query is the same.  The working report has the related tables added as additional columns as "value".   So, these columns we are missing are the foreign keys in the table we are querying.   Why would these not be showing?

Ideas?  How do I reset this?

Thanks for your time in advance,

lisa

[oldwoman]

I tried the above.  This did not save it.   We also tried to upgrade the drivers for the connection, no dice.  We also tried to specify azure, and then postgresql on the get data options in power bi.  This also didn't save it.   I verified I can do a join in datagrip using the same credentials, same tables.  Datagrip did not have a problem.   So, in short I verified the credentials and the database access.  I simplified the problem with a brand new report and just tried to retrieve the table and the relational table.  I see this work on the old database, but no dice on the new database.  I can see the straight access to the database table with data on the new database, but no relational links will come up.  Thanks for your time.   No need to post a reply.  I think our choice is to bail out of powerbi as our display tool.  For others that might see this problem, there is a work arround to use sql to retrieve the data directly.  We just have to many reports to back fill in this way.

[Anonymous]

Hi @oldwoman ,

Here are a few steps you can try to troubleshoot and resolve this issue:

1. Open the 'Advanced Editor' from the 'Power Query' and verify if the M query is correctly pointing to the new schema. Even though the M query might look the same, ensure that the schema name is updated everywhere it's referenced.

2. If the navigation step is not bringing in the relationship columns, try removing and re-adding the navigation step. This can sometimes reset any issues that occurred during the change of the data source.

3.Ensure that you have refreshed the data after making changes to the data source and schema.

Best Regards,

Neeko Tang

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