Forum Discussion

PeterGoertz's avatar
PeterGoertz
Frequent Visitor
11 months ago
Solved

Getting "Failed to execute 'ariaNotify' on 'Document': Failed to read the 'priority' property from '

When assigning a Target(this is a table in a lakehouse) in a DataFlow, I get this error message: ---------- Message ---------- Failed to execute 'ariaNotify' on 'Document': Failed to read the 'prio...
Dataflow
  • Anonymous's avatar
    Anonymous
    11 months ago

    Hi PeterGoertz ,


    Thanks for confirming. Since the flow runs fine after ignoring the design-time error, it’s indeed pointing more towards a front-end regression than a data issue. To help Microsoft prioritize a fix, I’d still recommend raising a support ticket and attaching your session ID. That way, the product team can trace the exact failure and speed up resolution.

    Meanwhile, glad to hear your workflow is executing successfully in spite of the popup. Hopefully, the engineering team rolls out a quick patch soon.

    Thanks,
    Akhil.

Anonymous's avatar
Anonymous
Not applicable
11 months ago

Hi PeterGoertz ,

Thanks for your input. I did validate the column types already even reduced the target to a single column/row with standard types but the issue still persists. The error message itself

Failed to execute 'ariaNotify' on 'Document'. The provided value 'none' is not a valid enum value of type AriaNotifyPriority

Points to a Fabric Dataflows Gen2 front-end bug introduced with the latest release. The mashup script runs fine, but the web client fails when it tries to announce a status update with "priority" "none", which isn’t allowed in the FluentUI control.

So while checking types is always a good practice (especially for parquet vs. SQL/Python agent compatibility), in this case the root cause is the UI regression.

Go ahead and raise a support ticket with Microsoft and include the session ID so the product team can trace it. To raise a support ticket with Microsoft so the issue is officially logged and can also help influence future improvements:
Create a Microsoft Support Ticket.

Thanks,
Akhil.

  • PeterGoertz's avatar
    PeterGoertz
    Frequent Visitor
    11 months ago

    Hi v-agajavelly, Thank you for you comment. I reckoned that ignoring the error and save & run leads to the desired result. The workflow is running although in design mode the error keeps popping up. Let's hope there's a quick solution to this bug.

     

    Kind regards and again thanks,

     

    Peter

    • Anonymous's avatar
      Anonymous
      Not applicable
      11 months ago

      Hi PeterGoertz ,


      Thanks for confirming. Since the flow runs fine after ignoring the design-time error, it’s indeed pointing more towards a front-end regression than a data issue. To help Microsoft prioritize a fix, I’d still recommend raising a support ticket and attaching your session ID. That way, the product team can trace the exact failure and speed up resolution.

      Meanwhile, glad to hear your workflow is executing successfully in spite of the popup. Hopefully, the engineering team rolls out a quick patch soon.

      Thanks,
      Akhil.