Forum Discussion
DM_GWPipeline_Gateway_MashupDataAccessError
I found the "issue".
The excel file data was coming from a unique sheet having dates as headers for different topics. In this case, the revenue headers were the same as sales headers (month dates for 2022). I think this was hard to process for PBI because it writes the first 12 columns as 31/1/2022 - 28/2/2022 - ... - 31/12/2022 but the next 12 columns as 31/1/2022_<numberX> - 28/2/2022_<numberY> - ... - 31/12/2022_<numberZ>. I need to delete those numbers (logically) but it seems the server do not read nor create those numbers. As you say, creating a dataflow this might be solved.
Thanks!
Marc
Hi Anonymous - it is difficult to help without complete knowledge of the Excel files and MySQL tables. Would you please consider opening a support ticket so Microsoft can help investigate.
If I was to try something, I would explore importing the different sources into separate table in a Dataflow, and then merge the tables from the Dataflows. This would allow you to revert to the "Organisation" privacy setting.
The message Column "31/1/2022" of the table would suggest that need to unpivot columns to rows somewhere, and the "31/1/2022" was hard coded instead of dynamically referenced.
I found the "issue".
The excel file data was coming from a unique sheet having dates as headers for different topics. In this case, the revenue headers were the same as sales headers (month dates for 2022). I think this was hard to process for PBI because it writes the first 12 columns as 31/1/2022 - 28/2/2022 - ... - 31/12/2022 but the next 12 columns as 31/1/2022_<numberX> - 28/2/2022_<numberY> - ... - 31/12/2022_<numberZ>. I need to delete those numbers (logically) but it seems the server do not read nor create those numbers. As you say, creating a dataflow this might be solved.
Thanks!
Marc