Create different kind of Accounts

[Snipa]

Hi,

I would like to know if it is possible to create 3 kind of accounts. We different kind of clients, therefor, we need different kind of informations on each clients.

Thanks in advance

Olivier

[christianknoll]

Olivier,

it certainly is. What you need to do is to create custom menuitems to identify what kind of yccount you are creating and with that eg. add a custom request to the account creation link. Parse that link in a custom controller you need to build for the accounts module and in that custom controller decide which view you choose. Define your three differnt views as editview1.def, editview2.def, editview3.def and choose the proper one. Displaying an account follows the same rule ut you can read the type from the bean rather than the request. You need to do this carefully with the caching that can produce funny results in such a setup.Dis a similar thing once for types of calls (yet I did end up changing that in the end).

The alternative solution is to include a custom footer in the view. So reduce the view to the bare minimum and add a custom footer.

All of the above relies on purely PHP. Alternaitvel you can also of course utilize JS and handel ti that way.

christian.

Hi,

I would like to know if it is possible to create 3 kind of accounts. We different kind of clients, therefor, we need different kind of informations on each clients.

Thanks in advance

Olivier

[susiewilliams]

What about just creating two additional modules (using Module Builder) that use the Company template as the starting point? You can add fields specific to each type of account to each module. For the third one, you could either use the existing Accounts module and add/remove the fields you want, or create a third custom module, modifying it similar to the other two you created.

[christianknoll]

i theory this is nice and easy but practically you create pile of issues this way ...

- what about linking all related activities etc. This will mean adding these two modules to the parent type relationships so you can e.g. track calls or create meetings. Not sure if Studio even supoports that. And in modules likes note there is no support except with ugly modification of the core code.
- Roles and Access control: to some extent this might even be a benefit since you can be more specific to grant which right to which user but still have a lot mor to maintain
- import: when you import you ave to run this three times
- joint database and check for duplicates: this will not work if there are different moduels
- ... lots of more reasons to use a simple type for the account ateer it that way ...

;-) .... christia.

What about just creating two additional modules (using Module Builder) that use the Company template as the starting point? You can add fields specific to each type of account to each module. For the third one, you could either use the existing Accounts module and add/remove the fields you want, or create a third custom module, modifying it similar to the other two you created.

[crmbalah]

Hi
try to add Account Type file in the account module and place the account type,
you can change your account functionality based on this account type

[ptemplin7]

I'm with the last post by Oliver.

If you really need for user to only see parts of the screen start programming the custom views. It actually isn't that hard but can get messy. Also remember that the studio allows you to put data inoputted into blocks this way you could just create the three blocks with info for each different type. Only fill out the one you want. All shared info would be int he default first.

Christians's suggestion would then allow you to only display the block you want. You can set this up with a trigger. See the Wiki for more info.

thanks Paris
Templin Computing LLC

[Snipa]

Hey guys,

thanks for all these answers.

But my problem is that I need 3 kind of Accounts, for example, buses ; trains; building. Because they each have different info I wanna have on them. Number of buses, routes, etc. But I don't need this in buildings, so I don't want to have only one account (for the 3 industries) with 100 of different fields who are useless half the time.

Hope this help, because I have tried creates 3 different accounts, and like someone said, this create a whole lot of other problems.

Thanks

Olivier

[christianknoll]

As I mentioned - create three views on one object and only show the field necessary and steer them through a custom controller. If there is only a subset of commn fields consider adding three individual tables with a foreign key. Nicer from design but adds further complexity ...

The alternative is to create three modules but again - I just see problems arising there and would not recommend that ... all the best, christian.

Hey guys,

thanks for all these answers.

But my problem is that I need 3 kind of Accounts, for example, buses ; trains; building. Because they each have different info I wanna have on them. Number of buses, routes, etc. But I don't need this in buildings, so I don't want to have only one account (for the 3 industries) with 100 of different fields who are useless half the time.

Hope this help, because I have tried creates 3 different accounts, and like someone said, this create a whole lot of other problems.

Thanks

Olivier