Many thanks for this you made a much stronger case for Subforms than I had anticipated... if it wasn't for that 200 record limit I'd be sold on them... but I'm afraid of creating a problem for the future. If you could export the subform from every record simultaneously so you could use it as the basis for a future import to a new module should we find we are hitting the limit that might be enough to negate the worry... some pondering to do I think.
Hey John! If you end up using subforms, and want to move them to a custom module related list later, you'd be able to export them via CRM Reports, or Zoho Analytics (if you have access to that app with your current licensing).
We are testing Zoho One. It’s looking like we will need a custom module in CRM to track the computers we repair for each contact. We will have to export existing data from QuickBooks Projects with no more than 20 fields per project/computer with up to dozens of projects/computers in business contacts. Seems like Subforms will be the winner for us. The computer information needs to follow through contacts, invoicing and books (needing only 1 or 2 identifying fields to follow). History of Zoho invoicing details needs to circle back to CRM Contacts. This seems like it would be possible!
Hi AbsoluteComputers. Sounds like a great use-case for Custom Modules! Make sure to add a field to your module for tracking the Device ID or Serial Number so that you can connect future services directly to those Devices.
I have to say I dislike Subforms. Subforms lack history tracking which is always a massive red flag and subforms UI is not great. You have to scroll to the subform to see if there is any data where with a related list you can quickly see the count
Could you do another one of these videos for the decision between Layouts vs Custom Modules?
Sweet video. All content, no fluff
Many thanks for this you made a much stronger case for Subforms than I had anticipated... if it wasn't for that 200 record limit I'd be sold on them... but I'm afraid of creating a problem for the future.
If you could export the subform from every record simultaneously so you could use it as the basis for a future import to a new module should we find we are hitting the limit that might be enough to negate the worry... some pondering to do I think.
Hey John! If you end up using subforms, and want to move them to a custom module related list later, you'd be able to export them via CRM Reports, or Zoho Analytics (if you have access to that app with your current licensing).
We are testing Zoho One. It’s looking like we will need a custom module in CRM to track the computers we repair for each contact. We will have to export existing data from QuickBooks Projects with no more than 20 fields per project/computer with up to dozens of projects/computers in business contacts. Seems like Subforms will be the winner for us. The computer information needs to follow through contacts, invoicing and books (needing only 1 or 2 identifying fields to follow). History of Zoho invoicing details needs to circle back to CRM Contacts. This seems like it would be possible!
Hi AbsoluteComputers. Sounds like a great use-case for Custom Modules! Make sure to add a field to your module for tracking the Device ID or Serial Number so that you can connect future services directly to those Devices.
Great video!
I have to say I dislike Subforms. Subforms lack history tracking which is always a massive red flag and subforms UI is not great. You have to scroll to the subform to see if there is any data where with a related list you can quickly see the count
That is an absolutely awesome video. If you would have told me to pay 5$ to watch it. I would have been willing to.