Hi Guys,
I have an internal CRM where I manage campaigns run in the company.
The front end is currently used by Internal Team.
I want to display certain contents of the CRM to my other end user, who are creators. It will be using the contents from same Database as CRM.
Should I use the Same app to do it? Or should I create a copy of My CRM app and then do the new UI.
I am not sure what’s the best practice. Can you guys guide me?
Thank you in Advance
Regards,
Dilip
Hi Guys,
Any suggestions on how can I approach this?
Thank you in advance.
Regards,
Dilip
I think it comes down to personal preference and what’s easier to maintain in the long run. Questions to ask yourself would be if you need to present data from the same table differently for front end and back end users, if you have to deal with several different row owner and role situations, or if you would have to deal with a lot of visibility and/or filters to present data differently.
I don’t think there is a right or wrong way, and there isn’t necessarily a standard best practice. You need to write out your flow from each perspective and see if a lot of it overlaps or not.
Thank you for responding Jeff. So you are saying there is nothing wrong if I create a copy of my CRM app and make a front end for my creators showing only feature they can view.
By essentially copying the data updates simultaneously in both tables.
I would want the creators app to be named differently its one of the other reasons I wanted to take this approach
This wouldn’t be a wrong approach right? Just asking from entirely guidelines perspective.
By any chance is there a way I can still keep the database and connect it to a different UI, meaning a new app with different name ?
Regards,
Dilip
Which database are you referring to? If you’re using Glide’s data tables, you have the option of linking them, where changes in one app are also reflected in the linked table in another app.
Hi Himaldin,
Thank you for replying. Yes I am using glide database.
How do you link it?
Is it by duplicating it and then selecting some option in there
Regards,
Dilip
There’s nothing wrong with it. Like I said, it all depends on what’s easier for you in the long run. I have cases where I have multiple apps that share the same database. In other cases I have everything in the same app. Just depends on your particular case.
Definitely. You can duplicate an existing app, keeping the same data source, and modify the duplicate, or you can attach existing takes to a new app. Either way works.
Hi Jeff,
While I understand how duplicating can be done
How can I do this?
Regards,
Dilip
Hi Himaldin,
Got it. Let me try it. Only basic columns will be available? ill have to create the other computed columns?
Regards,
Dilip
Yeah. Each application is unique to Glide. I really love this options like sharing libraries, videos between applications, and others within one team. If you ever change your mind, you can unlink the table. I think you don’t need to hesitate anymore.
If you duplicate an app, the computed columns will come along into the duplicate app, but only that one time. Any new computed columns will need to be added to both apps.
If you are linking a table, you will need to recreate all computed columns.
Thank you for replying Jeff.
Can I delete tables in Duplicated app which are not relevant ?
and when I do it it wont delete in the Original app?
Regards,
Dilip
Thank you for the reply Himaldin I just tried it. Yeah it’s amazing actually.
Only drawback was the computed column issue.
Regards,
Dilip
The best way is for you to duplicate your application and unlink the unwanted tables to be linked, including deleting the rowID.
You can unlink them, but you can’t delete them if they are used by another app.
Why would you delete the Row ID column?
Sometimes there is old data stored in the ‘usc’ column that cannot be detected. I experienced this coincidentally when the user and items happened to use old rowIds.
I guess I would be careful if those RowIDs are required to establish relations with existing data in multiple tables.
Thank you for this information Himaldin. I’ll just unlink it after duplicating.
Regards,
Dilip
