Forum Discussion

GilesWalker's avatar
GilesWalker
Skilled Sharer
10 years ago
Solved

The Csv.Document parameter 'Columns' is invalid.

Hi everyone,   I am having the following issue on a couple reports I have built. So far the only options on the community forums is to either change from a personal gateway to an enterprise one (Th...
Need Help
  • GilesWalker's avatar
    GilesWalker
    10 years ago

    My IT department managed to fix the issue. We went through the advanced editor in query mode and manually changed the coding to get it to work.

     

    This is how we did it:

     

    This line of text is incorrect:

     

    Imported CSV" = Csv.Document(#"Combined Binaries",[Delimiter=","columns=10, Encoding=1252]),

     

    The columns=10 was counting the columns in the document (10 is correct) but something was going wrong. We deleted this text but lef tin the commas and republished the file. It then failed again due to this error:

     

    The Csv.Document parameter 'QuoteStyle' is invalid. From memory the advanced editor text looked like this:

     

    Imported CSV" = Csv.Document(#"Combined Binaries",[Delimiter=","columns=10, Encoding=1252]), QuoteStyle=QuoteStyle""

     

    We deleted the QuoteStyle text and republished. The dashboard now refreshes using the automated refresh feature in Pro.

     

    Thanks,

     

    Giles

Caitlin_Knox's avatar
Caitlin_Knox
Advocate III
10 years ago

 

I get the error 'Token Comma expected' When I click show error, it highlights the text as shown in the screen capture. But looking at the lines around, I cant determine where it is expecting a comma.

GilesWalker's avatar
GilesWalker
Skilled Sharer
10 years ago

Caitlin_Knox

 

This happened to me also. By changing the inormation in the first couple steps this can then have an effect on the remaining steps. Is it possible for you in the query editor to remove all steps after the promoted headers step? Then see what the data looks like and go through and do your editing again?