Details about this thread
  • State Not Answered
  • Replies 7 replies
  • Subscribers 311 subscribers
  • Views 3389 views
  • Users 0 members are here
Related content from around SugarClub

Fields visibility based on a dropdown number

Andrea Finlay

Hi, what would be the best way to configure the following example:

Let's say the business is a car service company, where a customer (Account) can have 1 or more cars. The company needs to record the last date when the oil and tires were replaced and when each of them will need to be replaced depending on the number of cars in an Account.

I need is to create a 'number of cars' field and if the number 1 is chosen, then 4 field for oil and tires appear (last changed and next due for each component), but if the 'number of cars' field is 2, then 8 fields for oil and tires will appear.

I am not sure if I need to create these field as 'Dependent' fields or if it will be better to use a formula... or if this is possible at all.

I have attached a sketch of what I am trying to achieve.

Thank you in advance,

Andrea

   

Parents
  • 0

    Dear Andrea,
    If you would like to get more from CRM to improve customer service and sales of related services, I'd suggest adding modules Vehicles, as Greg recommended, and "Vehicles Checks" (related to Vehicles and Accounts).

    In this case, you'll get more flexibility:
    - to see the full history of checks for a particular car, not only the previous one
    - to use the history of checks for prediction (e.g., finding out customers who require checks frequently than others).
    - to extend the set of check's types (check the battery, the cooling liquid, ...)
    - to configuring workflows on a particular check
    - ...

    I hope it helps you

    Integroscrm.com
    We make work in Sugar
    more convenient and efficient

  • 0 in reply to Mykola Bulava

    I agree with , because and Account can have many vehicles and vehicles many checkups using two additional very simple modules is best: one for the vehicles related to Accounts, and one for the checkups related to the vehicles.

    Careful with circular relationships though.

    Account-> Vehicle -> Checkups is fine and using the relationships you can find all the Checkups for a given Account, but if you also relate Checkups <-> Accounts you need to make sure that when a Checkup is related to an Account the Vehicle is also related to that same Account and vice versa, if a vehicle belongs to an Account all the Checkups for that vehicle should belong to that Account.

    FrancescaS

Reply
  • 0 in reply to Mykola Bulava

    I agree with , because and Account can have many vehicles and vehicles many checkups using two additional very simple modules is best: one for the vehicles related to Accounts, and one for the checkups related to the vehicles.

    Careful with circular relationships though.

    Account-> Vehicle -> Checkups is fine and using the relationships you can find all the Checkups for a given Account, but if you also relate Checkups <-> Accounts you need to make sure that when a Checkup is related to an Account the Vehicle is also related to that same Account and vice versa, if a vehicle belongs to an Account all the Checkups for that vehicle should belong to that Account.

    FrancescaS

Children
No Data