Is there some sort of trick to setting a partner that should of been set to IsPrimary but wasn't initially. It doesn't seem possible to set it manually. So I've tried sever methods through various APIs and have no such luck. One type of message returned is:
Error 5002 : entity type cannot be updated: EntityObject of type: Partner, id: <null>]
I'm just beginning to develop API applications with Sales Force and would like to do things right.
I would like to develop a VERY simple web application that will access some VERY simple salesforce data. Which I know can be done.
What I am confused about is how I should approach this from a Licenses stand point. If I want different users to view some queried out information that I would present on the web site, do I need to pay for a different user/email license for each. What's stopping me from using the same (say, web login, web@domain.com) each time the site accesses information from my company's SalesForce account?
I have some follow up questions, but I will hold off until I understand this basic set accessing.
I was wondering if anyone had attacked syncing SalesForces data with Microsoft Exchange's data.
As, I'm sure my company is simlar to many in that many of our users are constantly in Outlook and use Exchange as a backend to hold Customer addresses and emails in a Global Address list. Along with having pre-definded Email Groups i.e. USCustomers, that they can quickly send off a quick email to the group of USCustomers that would get sent to many external customer emails.
But at the same time we would like to use Sales Force's great power as our CRM package. I guess what it comes down to is...Is there anyway NOT to have to update a Customer's email in both Exchange AND Sales Force.
I'm just beginning to develop API applications with Sales Force and would like to do things right.
I would like to develop a VERY simple web application that will access some VERY simple salesforce data. Which I know can be done.
What I am confused about is how I should approach this from a Licenses stand point. If I want different users to view some queried out information that I would present on the web site, do I need to pay for a different user/email license for each. What's stopping me from using the same (say, web login, web@domain.com) each time the site accesses information from my company's SalesForce account?
I have some follow up questions, but I will hold off until I understand this basic set accessing.
I was wondering if anyone had attacked syncing SalesForces data with Microsoft Exchange's data.
As, I'm sure my company is simlar to many in that many of our users are constantly in Outlook and use Exchange as a backend to hold Customer addresses and emails in a Global Address list. Along with having pre-definded Email Groups i.e. USCustomers, that they can quickly send off a quick email to the group of USCustomers that would get sent to many external customer emails.
But at the same time we would like to use Sales Force's great power as our CRM package. I guess what it comes down to is...Is there anyway NOT to have to update a Customer's email in both Exchange AND Sales Force.
