The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
So I've been using a table in a Fabric WH for some months now which includes a column name "Customer No.".
Now I wanted to append from a differenct dataflow to that table and i get an error claiming this table has unsupported column names:
It is extremly unfortunate if such constraints are being added afterwards... and therefore breaking things that have been working!
Solved! Go to Solution.
Hi @chris__1,
Sorry for the inconvenience caused here. we truly appreciate your perspective.
I’d like to clarify that the tagging and solution-marking approach you’ve observed is part of our standard moderation policy
as you mentioned I’d encourage you to submit your detailed feedback and ideas via Microsoft's official feedback channels, such as the Microsoft Fabric Ideas. Feedback submitted here is often reviewed by the product teams and can lead ...
Thanks,
Prashanth Are
MS Fabric community support
Hi @chris__1,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
please @v-prasare , asking to "accept a solution" every 3 days is borderline spamming behavior and is counterproductive since people will disable e-mail notifications!
also: my comment was put under the labels "Show and tell" and "General Comment".
I was not seeking advise nor looking for a "solution" rather giving feedback that changing such basic table requirements will break things for your customers and like @lbendlin did put it so nicely " is a recent addition in the annoyance circuit"!
I am under the impression that having as much threads as possible showing an "Accepted Solutions" (even when not applicable) is more important than using this channel as means to get feedback from your customers and users.
Hi @chris__1,
Sorry for the inconvenience caused here. we truly appreciate your perspective.
I’d like to clarify that the tagging and solution-marking approach you’ve observed is part of our standard moderation policy
as you mentioned I’d encourage you to submit your detailed feedback and ideas via Microsoft's official feedback channels, such as the Microsoft Fabric Ideas. Feedback submitted here is often reviewed by the product teams and can lead ...
Thanks,
Prashanth Are
MS Fabric community support
Hi @chris__1,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hi @chris__1,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
yes, that "cannot contain spaces" restriction is a recent addition in the annoyance circuit.