I have a few questions that arose during the migration of my XP from Excel to HCMS:
Our client wishes to be able to enter and edit content by himself. Since it is not possible to hide or freeze specific rows for an additional user of a Base, there is always a risk that the client might accidentally delete and/or modify content in one or more components that does not concern him.
Is there a fallback solution for such cases? I could, of course, create a duplicate of the Base—but how would I then apply that duplicate within the Experience? As I had expected, simple renaming does not do the trick.
The ideal answer would be to have very high granularity Role Based Access Control added to our H-CMS, where you could give very specific read / write permissions to users.
This is in our product roadmap, but not expected on the short term.
In the meantime, a common solution can be to separate your H-CMS content into multiple bases. For example
A main base that contains general settings, content that should not be updated except by you or an “admin” among your customer’s team.
A “content” base that contains the content that can be edited by a broader set of team members => only share that base with them
In that second base, the users will still be able to edit all the fields of an item (you can’t freeze or lock a column). Nothing a good user training / short manual can’t fix
Regarding your solution, if the update can be manually synced by yourself, you could indeed provide a base copy for their team to update. You can them export the collections content into a csv, copy the updated info into your own csv (the one with all the columns for the real base), and import that csv. That’s more manual, but more bulletproof since you’d be reviewing their content before publishing it.
Hi Seb,
The idea of splitting the Base into multiple separate Bases has actually crossed my mind as well. However, that would mean an extreme amount of effort—something I still need to think over.
Unfortunately, since switching from Excel to H-CMS, the performance of the XP in Player classic has become noticeably slower and choppier. Images from the H-CMS, in particular, are displayed only after some seconds (but not always) and can disappear without any apparent reason.
The Composer, in particular, now responds to every input and change with an unbearable delay.
After every entry, 10 or 20 seconds pass before another action becomes possible again.
Is this a known issue? Is there a way for me to allocate more RAM to Intuiface?
Working efficiently is no longer possible under these conditions…
A part of the content is still being provided by Excel, while the majority already relies on H-CMS. Could this be the reason for the extreme slowdown?
No it is not typical to have such delays in assets loading. But there are factors that could cause the delay, such as file size, triggers/actions happening within the scene, and/or filters being applied.
I suggest reaching out to us via our support channel, on there we will ask you to share the experience with us and we will review to see what could be causing this.
