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,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.