La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
Thanks for sharing, it is so helpful to understand use cases to learn more about requirements and capabilities... and I am a huge fan of HubDB!
1 - With permissions, it is possible to create a user role that limits access entirely except to HubDB. This wouldn't count against any of your seats for paid users.
You can also limit to "view" for those that need to provide input and "edit" for those that need to make changes. As long as you don't give "publish" permissions, you can always revert to the last published version to remove any changes made.
2 - yes, I agree the permissions could be more nuanced, especially when it comes to deleting columns or rows. Again, IF someone deleted a column or row, it could be restored by reverting to the last published version (tested and verified).
In this case, you would want to restrict the users who can "publish" to the critical few.
I'm not saying you shouldn't proceed with your plan to use an API on a website page, but it is possible to do this entirely within the backend if you wanted to, without the added expense of the customization.
Hope this helps! If you do decide to go forward with the customization, I would add a post to the jobs board or join the developer slack to post the job there.
If you are a HubSpot Super Admin, I also recommend joining the Sprocketeer Community at Sprocketeer.community to connect with other Super Admins and find solutions there. 🙂
If my reply answered your question please mark it as a solution to make it easier for others to find.
@ChrisChiha If the page can make changes to the HubDB without an approval mechanism, what difference would this serve over providing direct acces to the HubDB table itself?
my question is essentially "why" do you want to do it this way?
If my reply answered your question please mark it as a solution to make it easier for others to find.
Two reasons actually: - For users who are outside of our organization and can't access our CRM - HubDB permissions are not fragmnented. The permission will enable all hubdb features to all involved users. (We can't restrict creating/deleting, which might cause some inconveniences)
Thanks for sharing, it is so helpful to understand use cases to learn more about requirements and capabilities... and I am a huge fan of HubDB!
1 - With permissions, it is possible to create a user role that limits access entirely except to HubDB. This wouldn't count against any of your seats for paid users.
You can also limit to "view" for those that need to provide input and "edit" for those that need to make changes. As long as you don't give "publish" permissions, you can always revert to the last published version to remove any changes made.
2 - yes, I agree the permissions could be more nuanced, especially when it comes to deleting columns or rows. Again, IF someone deleted a column or row, it could be restored by reverting to the last published version (tested and verified).
In this case, you would want to restrict the users who can "publish" to the critical few.
I'm not saying you shouldn't proceed with your plan to use an API on a website page, but it is possible to do this entirely within the backend if you wanted to, without the added expense of the customization.
Hope this helps! If you do decide to go forward with the customization, I would add a post to the jobs board or join the developer slack to post the job there.
If you are a HubSpot Super Admin, I also recommend joining the Sprocketeer Community at Sprocketeer.community to connect with other Super Admins and find solutions there. 🙂
If my reply answered your question please mark it as a solution to make it easier for others to find.
sept. 22, 20227:18 AM - modifié sept. 22, 20227:19 AM
Au panthéon de la communauté
Updating HubDB table
Résolue
Hi @ChrisChiha you could manage it in google sheets using export to CSV and then import the updated CSV. I had someone on my team who was just quicker with spreadsheets than HubDB and they preferred to make the changes that way.
It still requires a handoff in your situation though and isn't as elegant as an API.
Best of luck getting the API set up and running!
If my reply answered your question please mark it as a solution to make it easier for others to find.