Hi Nikhil,
I believe most of the credit bureaus requests can take different address types (permanent, residence, business, etc…). Based on the credit bureau implementation you need to provide the configuration. For example PA might be meant as permanent address to some credit bureau but for some other P might be permanent address. If some credit bureau accepts only one address then you need to provide configuration to have which address type J. Let me know if it is not clear. Thanks, Nazeer From: Nikhil Pawar [mailto:[email protected]] Sent: 26 May 2017 15:55 To: Dev Cc: Ed Cable; Nayan Ambali; Nazeer Shaik Subject: Limitation of use of code_value table Hello Devs, While building request for credit bureau, I came across a limitation of code- code_value architecture. Currently code_values for address module are not system defined. Hence, user has the ability to feed in any type of address type. However, to make credit score inquiry, we have to make use of a single address. As the code value (for address type )is user defined, we are not sure which address to pick up for constructing credit inquiry. I am sure, community must have faced this issue in some other context. So, as a work around we were planning to add an additional column in m_code_value table which would be named as key. This key field will help developers to use code_values without compromising on the generic architecture of code- code_value tables. In my case, I would be adding keys corresponding to address fields I am interested by adding address.address_line_1 , address_zip_code in keys column, to pick up values for address to be used for credit check inquiry. This would eliminate the ambiguity of which address type to pick up. Let me know what are your thoughts on this work around. Regards, Nikhil
