Validating fabric item name change

[ernestjessee]

Workload Manifest Schema Version (if relevant)

No response

Your Question

Users of our workload may rename assets using the settings ui. Because of the way we process our assets, we need to validate the name that the user enters. For example, we do not allow names to begin with a number. When we get the update request and the name is invalid, we are returning a statusCode of 400 (bad Request). I have also tried to return 406 (unacceptable). In either case, the Fabric UI continues to show the invalid name.

How can we reject the name change and have the UI revert? Is there a way to validate the name change in the client?

Context / Background

No response

Additional References

No response

[matanSchaumberg]

Hi @ernestjessee ,
Can you share some info (screenshots of the flow+HAR generically and requestID of the update specifically from fabric)
Thanks

[ernestjessee]

attached is a har file and a log. For these files, I renamed a decision from aD to 1aD which is invalid. Our midtier rejected the name and returned a 400 status code. A message appeared near the upper right of the screen saying that update failed. However, when I closed and reopened the asset, the name was 1aD

I am attaching:

• log file
• image showing the final state of the ui and artifact
• the request payload
• the response payload

github will not allow me to attach a har. If you can provide me a share to drop the har, I am happy to do so.

request.json
response.json

rename_error_but_changed.log

[matanSchaumberg]

Hi @ernestjessee ,
Thanks for the detailed information and repro, much appreciated.
We were able to identify why the UI ends up showing the invalid name even though the request fails, and we agree this behavior isn’t correct.
We’ll route this to the right owner when capacity allows and work on a fix so that rejected name updates properly revert in the UI.
We’ll follow up here once we have updates.

[ernestjessee]

Thank you very much [signature_transparent.png] Ernest Jessee From: Matan Schaumberg ***@***.***> Date: Thursday, February 19, 2026 at 4:43 AM To: microsoft/Microsoft-Fabric-workload-development-sample ***@***.***> Cc: Ernest Jessee ***@***.***>, Mention ***@***.***> Subject: Re: [microsoft/Microsoft-Fabric-workload-development-sample] Validating fabric item name change (Issue #262) EXTERNAL [https://avatars.githubusercontent.com/u/180180792?s=20&v=4]matanSchaumberg left a comment (microsoft/Microsoft-Fabric-workload-development-sample#262)<#262 (comment)> Hi @ernestjessee<https://github.com/ernestjessee> , Thanks for the detailed information and repro, much appreciated. We were able to identify why the UI ends up showing the invalid name even though the request fails, and we agree this behavior isn’t correct. We’ll route this to the right owner when capacity allows and work on a fix so that rejected name updates properly revert in the UI. We’ll follow up here once we have updates. — Reply to this email directly, view it on GitHub<#262 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGXXE2PEMHVIQJCIT3ARKU34MWAUVAVCNFSM6AAAAACVKJSVACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMRVHE3DSMZTGM>. You are receiving this because you were mentioned.

[ernestjessee]

When this is converted from a question to a bug, I would appreciate a link to that bug. Thank you

[ernestjessee]

any update on this issue?