Forum Discussion
Incorrect values in table imported from Microsoft Access
- 2 years ago
Thank you for that. I don't have an immediate answer for you but I think we can start from an assumption that powerbi has not suddenly started applying random factors when importing from Access.
Here's what I would do.
1. Attempt to completely confirm that we are looking at the same row. Can do this by importing all the data to powerbi and looking at rows in Data View.2. Focus attention on the particular column in Access. The nearby column BUCH_MON shows no problems. Is the Value field a calculated field? Is there any manipulation of the column taking place in Access (Date or time-related calculations, maybe?) Can you remove all formatting in Access and make all fields text type then import (either as Access or csv?
These are the sort of things I would look at
- 2 years ago
Hi HotChilli,
thank you for your reply. I have found the solution: In the query in Microsoft Access, I filtered a text column using * in the criteria section of the design view: for example [Not like "* DL *].
I noticed that Power BI does not recognize the * and needs % instead. If I replace all * with a % in the criteria area in Microsoft Access, the filter also works in Power BI: For example [Not like "% DL %"]
Thank you for that. I don't have an immediate answer for you but I think we can start from an assumption that powerbi has not suddenly started applying random factors when importing from Access.
Here's what I would do.
1. Attempt to completely confirm that we are looking at the same row. Can do this by importing all the data to powerbi and looking at rows in Data View.
2. Focus attention on the particular column in Access. The nearby column BUCH_MON shows no problems. Is the Value field a calculated field? Is there any manipulation of the column taking place in Access (Date or time-related calculations, maybe?) Can you remove all formatting in Access and make all fields text type then import (either as Access or csv?
These are the sort of things I would look at
- David12052 years agoFrequent Visitor
Hi HotChilli,
thank you for your reply. I have found the solution: In the query in Microsoft Access, I filtered a text column using * in the criteria section of the design view: for example [Not like "* DL *].
I noticed that Power BI does not recognize the * and needs % instead. If I replace all * with a % in the criteria area in Microsoft Access, the filter also works in Power BI: For example [Not like "% DL %"]