How best to present extra data in Accounts?

Hi all,

In my Sugar installation, Accounts = customers. I have customised Accounts to include additional fields as per normal. The intention of my Sugar install is to act as a single place for data across my organisation and I have been busy importing and cleaning data submitted by colleagues as part of this process.

Now, however, comes a bigger challenge. I have a spreadsheet which has a ton of data on it. The data in question is employee information (headcount etc) about each customer, broken down into a range of different groups. So, it's nicely standardised, but there are around 20 columns of it.

The easy way would be to add those columns into the standard Account view, and import the data. But, that doesn't seem particularly elegant or efficient to me - particularly when it comes to users exporting the data and seeing a massive and confusing CSV.

So, is it possible to create a new module for this? That seems like a much tidier way to do it, but how can I import the data and ensure that the module's data is associated with each given customer?

Thanks for your help
Paul

Parents
  • Hi Paul,

    You can definitely do it that way. Once the fields are created in Module Builder and the package has been deployed, add a One-to-One relationship between Accounts and your custom module. You can then import the data into the custom module by simply adding one column to your import file. If you do not have duplicate Account names, you can use the name field and map it to the "Account" field. If names are not unique, you can use the Account IDs and map it to the "Account ID" field. Let me know if you have any questions!

    -Alan

Reply
  • Hi Paul,

    You can definitely do it that way. Once the fields are created in Module Builder and the package has been deployed, add a One-to-One relationship between Accounts and your custom module. You can then import the data into the custom module by simply adding one column to your import file. If you do not have duplicate Account names, you can use the name field and map it to the "Account" field. If names are not unique, you can use the Account IDs and map it to the "Account ID" field. Let me know if you have any questions!

    -Alan

Children