Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
I am wondering if anyone has come across this before. We have 4 seperate databases that are all setup with the same table structure. I am pulling from the data for general ledger transactions from each of them as seperate queries for the past two years. When they are seperate, the summed value for all of the income statement accounts are rock solid. Each refresh shows the same answer. When I append all 4 of the queries together as a new table, each time I refresh I get a different result in the combined table for periods in the past that are closed.
Anyone have that issue before?
Solved! Go to Solution.
My apologies for the delay in response here. I was on vacation when you asked the question and the email was lost in my inbox until now. I did solve this purely by luck. It appears that if you have conflicting privacy levels (and sometimes even not) the append will give different results. I turned off the following option in my reports and things stablized:
File=> Options and Settings => Options=> Privacy
From there I chose the other radio button option "Ignore the Privacy Levels and potentially improve performance".
Hello,
Did you open a ticket at Microsoft? Got any returns? I'm having the same problem, using the "append as new" option, the new table is different from the original tables.
My apologies for the delay in response here. I was on vacation when you asked the question and the email was lost in my inbox until now. I did solve this purely by luck. It appears that if you have conflicting privacy levels (and sometimes even not) the append will give different results. I turned off the following option in my reports and things stablized:
File=> Options and Settings => Options=> Privacy
From there I chose the other radio button option "Ignore the Privacy Levels and potentially improve performance".
Hello,
Did you open a ticket at Microsoft? Got any returns? I'm having the same problem, using the "append as new" option, the new table is different from the original tables.
Hi @zimmermanaric,
What do you mean by having different values for periods past that are closed?
How are you appending the tables and how are you calculating the result for the months that are closed?
Regards,
MFelix
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsHi! I am pulling the data into Power BI via Sql. There are only a few columns:
1. period
2. year
3. amount
The where clause in the sql statement is limiting it to year 2017 and higher. Then I am using the "Append as New" function in the Advanced Editor. Once done, I create a simple matrix table showing the value as amount, column as year and row as period. Each time I refresh, I get a different answer. The only account period that we have open is Feburary 2018. Prior Month's should be the same. This is only happening with a table that is appended from the 4 other tables. If I do the same matrix with each individual table, the numbers to not change on each refresh of the data.
Hi @zimmermanaric,
Sorry for the question but Why are you making new appends with several SQL and not a single SQL for everydata?
could it be possible that you are repeating data everytime you add a new query?
Regards,
MFelix
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsI really appreciate your thoughts! It is 4 sql statements that are written the same way, pulling the same columns and years, but connected to 4 differnent databases.
Did you figure out why this is happening? I'm having the same issue.
I have two queries being appended into one. Each time I refresh the values from the appended table change, even though the values in the original two queries stays the same.
No I have not. I think I am going to have to open a ticket with Microsoft to help with this issue.
I actually just fixed mine. In my original queries, I added an order by clause at the end. I don't know why this fixed it, but it did!
ORDER BY [TABLE_NAME].[COLUMN_NAME] ASC
Maybe this will fix yours as well? Good luck!
I really appreciate the update. Unforuatnely, I don't have an order by clause in mine.
Couldn't you just add one to the end of your SQL query? Just order by year or period maybe?
I am very sorry. In my haste I misread your post. I thought you said that you removed your order by. I will try it and let you know.
That reduced the magnitude of the change in the number, but it will isn't adding up correctly and changes every time I hit refresh.
Yes. I added the same order by to all 4 queries. How many columns are you selecting in yours? Did you order by all of them?
Hi @zimmermanaric,
First of all let me apologize for not responding on this message but add some issues witht work, and also lost the track to the treadhs I had open on my Inbox.
Can you please give some more details on your setup? To my experience when I add several SQL in PBI the only issues I experienced similar was when people where inserting data in the database so every time I refresh during my tests the data was changing.
Regards,
MFelix
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsHi! Inserting records is not the issue here. I am querying information in the past that should not be changing.
Check out the October 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
113 | |
96 | |
92 | |
84 | |
69 |
User | Count |
---|---|
160 | |
125 | |
116 | |
110 | |
95 |