Forum Discussion
Can not save Semantic model on specific folder
Hi akkibuddy7,
When you "Move" a semantic model in Fabric, it actually creates a copy in the target folder rather than moving it. Since it creates a duplicate, both copies consume storage separately. This can increase your storage usage, especially if the semantic model is large. It can have complexity with managing your data as any changes made to one copy will not reflect in the other, as they are independent. This can lead to version control issues if you're modifying different copies. It can also lead to workspace data redundancy as the original model still remains in the workspace, so you might end up with redundant models, making it harder to manage them efficiently.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi akkibuddy7,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like you want to create a semantic model based on an S3 shortcut table view (vm_test) but it is created directly in the workspace without giving an option for specifying a folder to store it. Also when you tried the "Move to" option, it created a copy instead of actually moving the semantic model. As of now, Microsoft Fabric does not support explicitly organizing semantic models into folders within the workspace. All semantic models are created at the workspace level. Since you cannot move or save semantic models in specific folders, what you can do is to create separate workspaces for different projects, departments, or logical groupings of data models.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.