Forum Discussion
Excel import not consistently recognising blank first column
- 1 year ago
Thanks - I tried setting InferSheetDimensions to false but you're right it still uses excel's used range. I don't have control over the file creation unfortunately but I can interfere if a file is recieved and breaks the flow. A bit faffy - hopefully a feature to control the import is added soon. Thanks!
Thanks - I tried setting InferSheetDimensions to false but you're right it still uses excel's used range. I don't have control over the file creation unfortunately but I can interfere if a file is recieved and breaks the flow. A bit faffy - hopefully a feature to control the import is added soon. Thanks!
Can you try setting InferSheetDimensions to true instead of false? The default is false, so setting it to false won't change anything.
- poinfrettia1 year agoFrequent Visitor
Ah it was already true, I thought that was the default? It seems like neither way changes it regardless unfortunately.
- Ehren1 year ago
Microsoft Employee
Ok. Then your best bet would be to write logic in M that detects whether the data starts in Column1 vs. Column2, and handles both cases.