I really need this to enhance my apps.
@Mark, shared data tables between apps does seem very useful for app development and deployment. I am +1'ing this topic for that reason.
For the rest of you, would it not make more sense to have one app that encompasses each component all in one? (Forgive me if this is a dumb question, I'm new to Knack, and so trying to learn some best-practices)
Keen to see this, good idea.
This is mandatory feature knack is lacking of.Ā
If implemented, this would help with having a better deployment methodology. Right now you can copy apps without data to another new app which is how I'm currently doing production deployments. Right after I copy the app, then I copy all the existing production data into the newly created app. If I could have this new app use shared tables instead, then as soon as I deploy, the new, updated app would have all the existing prod data, which would save me a troublesome step and make production deployments much easier.
This is something we fundamentally need. We need to track prospect list to market, prospects we are engaged in selling to, customers who have purchased. The company, contact information needs to be common to all 3 apps
I would also agree that this is a large need, it is one of the only advantages I see that Salesforce has on Knack.
Would love to see this in the new year, would make Knack so much more useful!
Any update on this? Ā I have this need as well. Ā I'm working on various apps for my business and I'd like to have a central set of tables for our employee list, departments, office locations, etc. Ā Each app will have a specific use, but several will pull from these shared data sources. Ā It wouldn't make sense to duplicate the data across all our apps.
It is a great interest for Knackās financial benefits to implement this requested feature.
Once this feature is in place, a Builder will separate his/her one big App into multiple Apps. Very quickly, he/she will run out of App quota, and has to upgrade.
Yes!! This would be SO HELPFUL!!! I spend so much time setting up weird Zapier workarounds to update apps with data from other apps - it would be so much easier if we could directly connect objects and share records across apps.
Iām new to Knack - and really shocked this is STILL not possible, this thread was created in 2014 and it is now seven years later. The value of using data is enhanced when it can be reused so being able to access the same object (instead of separate copies of data) in multiple apps is fundamental - and surely a straightforward requirement.
Please prioritise this.
This is definitely a requirement and I would be very interested to see some movement on this request. It is not always feasible to build a mega system just to be able to share data between separate business units. Why are we still having to create workarounds, and duplicate data from one application to another? This goes totally against the grainā¦
Hi! just following up here. Will this feature be in a future update?
Please add this feature, there are common database to used between different application, of else add a Task functionality to sync the similar database on different applications
I plan to offer users the option of a Custom version of my App, built by copying the App to a new App, copying at least one table, then modifying as requested. It would be better to link the table, even if temporarily for a simpler copy than export/import.
I vote for this feature.
Hello all! My name is John Karas, and I lead Knackās Product team. Thank you all for the discussion and feedback here⦠Good news: This is a feature that weāre scoping out now and officially have this in our Roadmap!
Be on the lookout in the Forums, in our email Newsletter, and in new areas of the Knowledgebase for more as we progress this.
Keep on Knacking!
Hi @JohnKaras! THIS IS A HUGE NEWS!
It will support the Single Source of Truth concept, and highly boost the use of Templates.
Go Knack!!
@JohnKaras - I was very excited to receive an email that this is going live in a week or so! Such great news. One question I did have about it, is the MongoDB schema limit still applicable just per App? Or does it now apply across the whole account/database? Does this change mean that limit has been overcome with a new underlying architecture?