I'm going to ask a few - I think - fairly fundamental questions here, so please excuse my ignorance...
We are considering using a 3rd party website to gather data that will initially be held in the 3rd party database before ultimately being written into to CRM using the Web API.
At the moment, it's essentially an application form for a club. The applicants answer a series of questions on the web site, this is then written into the database (from here the data goes to an application and CRM - hence the "holding" database model) and then it needs to find its way into CRM.
My remit is to ready CRM for this data but I'm not sure exactly what the 3rd party (people writing the API routine) will need - and they don't either at this stage as they haven't used the API before. A simple example:
I've created a custom entity - Application Form. This is where a lot of the data from the website will end up. Things like - application number, referral information, etc all clearly belong in this entity but other information that's being captured -eg: contact information, company information etc - clearly belong in Contact and Account respectively. How do I manage this? If I were dealing with just the CRM aspect of it, it would be simply a case of lookups from one entity to another, but when having to accomodate the 3rd party data and how it's written to CRM, I have no idea.
I hope this makes sense, and welcome any advice/comments...
Thanks in advance..
*This post is locked for comments