Forum Discussion
Dataflow Gen2 - Query name cannot contain the following characters: " \ / : | < > * ? '
I'm not sure how you are ignoring the warning - it should prevent you from saving the query name if it has invalid characters. Can you clarify that?
As far as the implications - we have this validation to prevent issues with downstream consumption due to inconsistent support for special characters. I would definitely recommend renaming the tables to exclude prohibited characters in the query names, as it will lead to other issues.
I am converting a Power BI Legacy dataflow to Dataflow Gen2 and the table names in legacy had : and / characters. There were no warnings in legacy.
Interestingly, dataflow gen2 throws a warning but allows to publish the dataflow -
This is what we want, as we have 69 tables in the legacy dataflow and the corresponding dataset is conected to 130 plus reports.
But when applying the destination, the mapping removes the special characters -
This is also fine for us as the dataset will seamlessly point to dataflow gen2 and external teams can access the tables from the lakehouse using SQL endpoint and is okay with the new names
So we hope dataflow gen2 can continue allowing the use of special characters just like legacy dataflow.