Forum Discussion
If then statement, invalid identifier
Ok, that makes some sense, but in no version of the query that returns an "invalid identifier" error does getting rid of the "" on 296 get rid of the "invalid identifier" error. In some cases taking the quotes off of "296" just moves the invalid identifier to the 16942, but that one IS text because many fangraphs IDs begin with "sa".
Hi coreych,
This is Ok, the field can be text, it should not be a problem.
Did you try this version of the replacer? What it returns on the "296" lines?
You can try using this knowledge for tweaking the actual replacer code.
Cheers,
John
- coreych3 years agoRegular Visitor
I don't really understand what the x,y,z is doing. I think you wanted me to replace that with the values. I wrote it this way and it returned the "invalid identifier" error on the first "16942" parameter.
...
#"Replaced Value" = Table.ReplaceValue(#"Removed Columns", each [Index], null, (“16942”,296,null)=> {“16942”, 296, null}, {"Player IDs.IDFANGRAPHS"})