Forum Discussion

mmoroni's avatar
mmoroni
Helper I
5 years ago

PowerBI and Smartsheet refresh error

So our organization has a few users working on a .pbix file.  Within said file, it has a data source that was linked with Smartsheet.  The user that first set the source can operate and refresh just fine.  Howevere, if a 2nd user accesses teh .pbix, they can manipulat eteh data with no issues - however, if they attempt to refreshg the data, it errors out with a statment "

MDU LOCATIONS Smart Sheet
The key didn't match any rows in the table.

I am thinking that the key for teh specific sheet is tied with his smartsheet user.  I am the actual OWNER of teh smartsheet, but the other employee is teh one that linked the source.
 
Is there a way to have multiple users be able to refresh the data at will in the .pbix?

2 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi mmoroni ,

     

    Smartsheet uses the OAuth authentication standard.  So it's up to that third party app (Power BI) to determine when the token needs to be refreshed and recognize the user is logged in on a different browser tab.

     

    Usually this means you are trying to connect to a table or worksheet or something in your data source that has been deleted or been renamed.

     

    Double check columns and sheets. Make sure there are no leading or trailing spaces in column and sheet names,

    and you've set the correct user with sufficient premission in the data source of your gateway. If the user is correct, try to delete and re-create the data source. If it still doesn't work, try to save your pbix in another name and publish it as a new report.

     

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

  • jane01's avatar
    jane01
    Frequent Visitor

    I am also coming across this issue - we publish reports for other users and want to set up refresh credentials using our service account. Smartsheet isn't allowing us to sign in as a different user. I agree it seems like the keys are somehow linked to the users credentials, as the source sheets have definitely not changed or been renamed