Forum Discussion
Shortcuts
tan_thiamhuat likely the Microsoft documentation is outdated. Changes in Fabric happen all the time and much faster than the docs are updated. I would not be surprised if some time ago that documentation was true.
Hi tan_thiamhuat, very interesting question. I am not sure, though, why you are asking this question: do you have any particular reason to use spaces in your naming convention? I would strongly suggest that you should not.
Delta tables and other objects on OneLake are stored in OneLake file system that may support spaces in object names. But apart from that you have Lakehouse interface, and SQL endpoints, and REST API URLs, Git integration, etc. that may have way more restricted approach to spaces. Again, I strongly suggest you should not use spaces in any object naming conventions in Fabric even if it may be tempting because it's supported in one or another scenario. If you want to separate individual prefixes, suffixes or words in your object names use underscore _ as a proven well working approach.
If you find this answer useful or solving your problem please consider givint it kudos and/or marking as a solution.
no particular reason to have a space in the name, but I am just testing it and even with that space, it is still able to create shortcuts, unlike what the Microsoft document mentioned that it cannot.
tan_thiamhuat likely the Microsoft documentation is outdated. Changes in Fabric happen all the time and much faster than the docs are updated. I would not be surprised if some time ago that documentation was true.