topic Re: Dataflow gen2 does not work with 'optional' as a column name!? in Dataflow

Dataflow gen2 does not work with 'optional' as a column name!?

Jalalmn — Wed, 28 Aug 2024 09:48:09 GMT

When publishing my dataflow it returned error during the publish stage. Unfortunately without any helpful logs.

It was a tedious task to find out why my dataflow instance does not get published.

First I started to remove tables one by one from my dataflow list of tables, and tried Publish, to figure out which table is problematic.

I found the culprit table!

Then I started removing its columns one by one to see when it pass the publish!

And finally found the reason, and guess what!? The name 'optional' as a column header is not accepted!

It was hard to believe, but I tried to rename a column name in a good working (publishable) table to 'optional'. And guess what? It failed publishing.

Is it just for me?!

PS:The funny part was that I am working with tables having mixed German/English titles and columns, and I was mainly suspicous of those with non-English names. But finally the 'pure English named one' turned out as the source of error!

Best,

Jalal

Re: Dataflow gen2 does not work with 'optional' as a column name!?

lbendlin — Wed, 28 Aug 2024 21:05:11 GMT

Funny indeed, and not mentioned anywhere in the documentation. Who knows what else is reserved.

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

Re: Dataflow gen2 does not work with 'optional' as a column name!?

miguel — Wed, 28 Aug 2024 21:50:47 GMT

Thank you for raising this issue! The team has confirmed that this is a bug and are currently working on a fix.

Will update this thread once there's a timeline that I can share for the fix.

In the meantime, the only alternative is to not use the keyword "optional" in your columns or queries.