Welcome to Portal
Thank you Andres for taking the time to give me an alternative solution. That is so nice of you!
Now I think I understood what you mean. So we use a dummy module with a subform just to add the subform to the linking module? We definitely would need a widget to present this information in the linking module then, otherwise it would be too complicated for our staff. Although I don't like the workarounds, this is an alternative if we can't get subforms activated for our linking module by Zoho support. It would cost us a lot of time and money for customization though.
Yes, the thing that annoys me the most, is that the limitation are so meaningless. Just like you said. I mean, why is a subform inside of a linking module a problem? I can't wrap my head around that.
Anyway Andres, you are the man, thank you!
Do you do Zoho consulting work or are you using Zoho for your own business?
Imagine, @Zohoboy! It’s a pleasure to help.
Actually, we are just adding an extra layer that will interact with the linking module.
I've created a video with the basic structure so that you can better visualize the problem, see attached.
In summary, the linking module "Module 1 x Module 2" has a lookup field pointing to the "Support Linking Module", where we have the entire necessary structure with subforms (and you can work on CPQ here). In this module, you can add references to Module 1 or Module 2 within the subform items in case you need to connect each item to its respective module.
And as you pointed out, the flow for the end user is a bit confusing and lengthy. One alternative to widgets (I always try to use them as a last resort) is to streamline this flow using a Kiosk, prompting the user to provide the necessary data to create the entire structure of the flow you have defined. From there, you would have to deal with the Kiosk's limitations 😁
I started implementing it in a business, but I also do some consulting. I consider myself a Zohoboy too!
If you need any further assistance, I’m available!
Subscribe to receive notifications from this topic.
Thank you for your comment. I really appreciate the input!
I understand that we could create a somewhat clunky version of a subform using a lookup. However, it wouldn't provide the same functionality or user experience as a true subform.
We use subforms extensively to generate lists of things that need to be done for a car. Introducing a related list would cause a significant disruption to the UI in our system.
Additionally, related lists are not as user-friendly as subforms. Creating a new record is much more cumbersome compared to simply adding a new row inside a subform.
With subforms, we can easily use aggregate fields directly beneath the subform. Related lists, on the other hand, can only appear in the details section or notes of a record, while rollup fields can only be placed in the details section as well. This results in information being scattered across the entire record, which is not an ideal solution.
Our users are workshop staff who need quick, easy access to all relevant information without having to search for it.