Column not populating

[Sam_Jain]

Hello Community,

I have a dataset which utlizies CSV files as their data source. The table consisits of 5 columns and one custom column which translates the date into the start of month. The format is kept consistent through out. I have 6 months worth of data populating and working fine. However the latest addition which was last 4 months combined together is where the issue lies. One of the columns notably spend draws a blank for those 4 months. I tried checking on the data view and even on the Query Editor. After my last step when i filter for the last 4 months it draws a blank. 

What could be the issue here?

It's a spend column, i've ensured all the data extracts are formatted to kept in General it has some negative entries but nothing that isn't present on any of the other months. I also have a step to change data type to currency.

Any help would be appreciated.

Thanks.

[Anonymous · Accepted solution]

• Are the first 6 and last 4 spend column names exactly the same?

[Sam_Jain]

@Anonymous Hello Nate,

Thank you on the response. The spend column does exist. Infact most of the viz use that field and now it draws a blank for those 4 months. There are no extra columns it has been the same way since the first upload 5 columns and that's how the code reads [Columns = 5] and then one custom column(month end date). They are all formatted to general on all the files. Yet, just for those 4 months it keeps drawing in a null.

I even tried on a new PBI file to import the csv (4 months) and it works (spend column). I just don't know why it shows up null when appended all together with past data on the original file.

The only inconsistency i see on all the raw data extracts is sometimes the number comes in as whole number, decimal and some negative.

[Anonymous]

Does the Spend column still exist? If not, it will show nulls once you append/combine them. If there is an extra column, and you have the number of columns specified in the source function (like [Columns = 6]) then you wont pick up any new columns.

I bet that if you remove the columns parameter from the Csv.Document, everything will fall into place.

--Nate