Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago

Report using composite model not working when published

My report is using the new composite model feature - one direct query connection and a couple custom tables. The report works and refreshes without issue in the desktop app, but when the report is pu...
Need Help
Anonymous's avatar
Anonymous
Not applicable
7 years ago

Hi Cherry,

 

Thanks so much for your response! 

 

I opened up the desktop app this morning and saw that I had an update available. I installed the latest version, republished the report, and am still experiencing the same issue.

 

The gateway is connecting without any problem, and this is listed under the Data Source Credentials section of the dataset refresh page: (admin has granted access, credentials are not required)

 

Thank you,

Sarah

v-piga-msft's avatar
v-piga-msft
Resident Rockstar
7 years ago

Hi Anonymous,

 

Have you solved your problem?

 

If you have solved, please always accept the replies making sense as solution to your question so that people who may have the same question can get the solution directly.

 

If you still need help, please feel free to ask.

 

Best Regards,

Cherry

  • Anonymous's avatar
    Anonymous
    Not applicable
    7 years ago

    Hi Cherry,

     

    What solved the issue was removing the custom tables in the desktop file, leaving only the direct query connection.

     

    The custom tables were ones created within the desktop file, and they were created to contain custom measures.

     

    I can't figure out if this is an exception for what can be done with "mixed" queries.

    • Eklavya's avatar
      Eklavya
      Microsoft Employee
      7 years ago

      Hi Shanshew,

       

      We recently fixed an issue with pasted tables in Composite Models that was causing refresh to fail when pasted tables were used with Direct Query tables. Would you mind checking if this issue is resolved for you now?

       

      If not, we can work with you to resolve this issue.

       

      Thanks,

      Eklavya