Keeping Track Of Loose Ends
Just keeping track of the things I need to come back to:
- MDM Server doesn’t like the TCRMPartyContactMethodBObj’s in my addPerson XML. I could add the phone number, but not the e-mail address. It complained that I was using either an incorrect contact method category or contact method type. My entries matched the code tables as far as I could tell. Just dropped the e-mail for now.
- The data grid in the UI seems to break now when I retrieve an unfiltered list of persons (roughly about 110 of them). But if I reduce the result set with search parameters, no problem. Odd. That was working yesterday even with a hundred names.
- This config is really taxing my poor laptop. Running the VMWare image, RMI Gateway, and sMash runtime causes my memory to start swapping out pretty badly. Definitely gets worse the longer I work with it.
- The UI doesn’t give very good visual indicators when requests are still being processed.
- The data grid looks a little barren because I’m only populating a handful of attributes. I might need to think a little more about which attributes display in what context. For example, TCRMPersonSearchBObj’s returned by the inList() service don’t have all the wrapper attributes, unlike the TCRMPersonBObj’s. Need to think about the right way to configure all of that.
July 30th, 2009 at 5:09 am
Insights from a colleague…
“I had a similar problem in the past. So, in your TCRMPartyContactMethodBObj, the ContactMethodUsageType attribute should match the CDCONTMETHTP code table and the ContactMethodType should match the CDCONTMETHCAT code table as I remember it. So, I was having problems because my ContactMethodType was pointing to a value at the CDCONTMETHTP as logic tells would be the correct code table, but it is not.
“Probably, your phone number is working because you have the same value in both code tables, but your email is not because you are using a value that exists in CDCONTMETHTP but not in CDCONTMETHCAT.”