Halty

Trouble with MSP Custom Mapping

Discussion created by Halty on Jan 17, 2011
Latest reply on Jan 25, 2011 by Chris_Hackett
I have been successful with custom MSP mappings for many attributes/data
types. However, I'm having trouble with 1 in particular. I've read
ca_recommended_clarity_msp_mapping_standard.doc and have taken its advice to
heart.

My problem is I cannot map a task field called 'tax_credit'. It's a 'numeric
lookup' datatype field of a 'yes' or 'no' value in the UI. I have mapped a
similar attribute successfully already. The one thing unusual about this
attribute is that it uses a parametrized lookup.

I have gone so far as to create a 'proxy' attribute that is a calculated
field of the 'tax_credit' attribute I'm trying to map, but it did not work.

I've tried to map 'tax_credit' to Number3, Flag10, Text30 in MSP and none of
them work. I have had no problems with the 6 other task attributes I've
mapped for MSP.

Has anyone out there experienced this before? Any solutions?

Thanks
Halty

Outcomes