Some recent new direct data loads I have added are saying "No columns to display".  I even exported one, added a new dataset with the initial headers only, and loaded the data in the month I needed manually, and the new one is also displaying "No columns to display".  I am in R12 and have been for some time.  Any thoughts?

Stacie,

Are you loading an excel file or csv?  Can you see the columns at any step or does it display the error at the import step?

Excel files could have an extra row that it thinks is the header row.  Or maybe a special character in one of the columns.  I've ran into this before but no recalling what the issue was.

Jeffrey

This is the error in the tables section

The first id the one I added as a new dataset, and the next one is the original load from Datalink.  The last is the transform I did of the load from Datalink.  It was when I added the transform and config that I noticed the error note in the tables section below the dataset.  

Add a "model" step to your pipeline

[edit] i was typing quickly on a call

I see this when the table in question doesn't have an associated model step.  In the table, add a model step, and that should allow the columns to show... that being said, it's not always healthy for the project to have a model step leading to nowhere, but it will get you over this particular hurdle

again, appreciate your patience as I typed my answer wayy too fast.

Thanks!

without actually looking at what you have going on -- there could be a 'version' in your table, and where you uploaded your backing file, it is in a prior 'version' ... i've noted situations where I have inadvertently created these scenarios, but I can't remember exactly because it's been a while.  I know I ended up using a brand new table & appending into my old table in order to get around that versioning issue...