Below is the profile. difficulty is to pass Field: Account.TerritoryNames.
I Set the Field Colum in Account Territory Assignment rule in BOOMI As (Account.DTE_TerritoryNames__c) which SF used to populate that field in SF
Are you asking what value you need to provide for the "Field" element in the Create TerritoryAssignment Request?
If so, I checked out the SFDC doc Salesforce Developers - AccountTerritoryAssignmentRuleItem but that description is not terribly informative as to what value it expects. What I would do is configure an assignment rule in the SFDC UI, then extract it through the API/connector to see what value is in that field so you know what to provide when creating a new one.
Thanks Adam, Checked With the Salesforce Team What Value they Have Used to populate that Picklist value. And Its Working. I have Concerns to implement it Server Side But Will Have to Check What the Business Requirements Demands.
Also I have a PICKLIST for Country Say about 200 countries to Check before passing the Country Coming from Source. I checked we could work wih Cross Reference Table in BOOMI to Handle this but its an overhead for Boomi. If It could be restricted from SOURCE ITSELF it would be more efficient ?
Glad to hear you got it working. What was the nature of the values you had to provide?
Regarding the picklist, if you need to do that validation in Boomi I would use a Cross Reference Table because it's the easiest way to maintain that number of allowed values. However if you can trust the data from the source, maybe you can skip the validation in the process and just handle errors from Salesforce if they happen.
For PICKLIST option, I would advise to go with the option of using CRT. There is not much overhead to Boomi since they are used only when required. This is the best option Boomi has and changes are easy to incorporate in CRT. Another reason is that as a Boomi developer always you will have an eye on all components instead of reaching out to different teams when there are changes.
Retrieving data ...