Re: camel-salesforce-maven-plugin picklist to enum generation

[kag <ki...@gmail.com>]

Any news on this?

Spwaned by this issue, we were having some discussions around the best way
to handle picklists. 

The default behaviour in salesforce is to allow any String to be added to a
PickList field (as far as I know),
regardless of whether the String is in the picklist or not. This means that
a Backend System can introduce a new PickList value, before it is added in
Salesforce.

Mapping the PickList to Enums in effect creates a hard coupling between the
backend system mapping and salesforce.

If you mapped PickList to String fields, would allow both the backend system
and salesforce to evolve "out of sync".
The String approach wouldn't be able to convey information on which values
are expected.

The Enum approach makes sense when you care more for the correctness of the
data, rather than getting the data saved.

We would like to have an option to whether picklist should be mapped to
String or Enums.

Have you had any discussions on this issue?
What are your thoughts on this?




--
View this message in context: http://camel.465427.n5.nabble.com/camel-salesforce-maven-plugin-picklist-to-enum-generation-tp5776908p5777740.html
Sent from the Camel - Users mailing list archive at Nabble.com.