Question
Adqura
TR
Last activity: 25 Jul 2016 2:25 EDT
Data type of CustomerID cannot be changed in Pega Marketing 7.13
Pega Marketing: 7.13
Pega: 7.2
This is an enhancement request directly from a customer. Customer is not satisfied with Pega Marketing's unique identifier property, CustomerID. Unique identifier's data type is varchar and it cannot be changed. Customer is requesting this value to be customizable as well. In their environment, in Oracle, data type of customer identifier is numeric and they would like to use the same column as is. Product management advised (https://mesh.pega.com/message/249456) CustomerID to be used as is, text value.
HFix-26452 already applied and Pega property CustomerID is mapped to customer's numeric unique identifier. It seems to be working. However, such an implementation may have an adverse impact. In other words, we are not fully aware of the downsides of such an implementation since it has never been tested.
Briefly, customer would like to be able to customize the data type of Pega Marketing customer unique identifier, CustomerID.
Regards,
p.s. Pega Marketing doesn't exist in the Product Topic Category.
Updated: 22 Jul 2016 11:55 EDT
Pegasystems Inc.
IN
Hi Oguz,
Thank you for posting your question here. We realize Pega Marketing is currently unavailable in the Product Topic Category list. We will consider including that soon!
Please click on the black feedback button on the right side of your browser window to submit this and any other feedback you have.
Do you mean to raise an product enhancement?
Hope to see you around the Community!
Lochan | Community Moderator | Pegasystems Inc.
Pegasystems Inc.
US
Hi Oguz,
I have submitted this feedback enhancement request on your behalf. I have also private messaged you the number for follow-up on your end.
Thank you!
Pegasystems Inc.
US
Oguz,
I'm not sure I follow. Are you saying you've already changed the data type, it seems to be working and you want it blessed? If it's working great, but if it's different than OOTB there is always the possiblity that will cause an unexpected conflict somewhere that could only be found through testing.
If you're more focused on there being an easy way to change the property's data type in a guardrails compliant, easy way, that can be passed on to product management, but I expect the type is varchar specifically to allow maximum flexibility. You want to only put numbers into the varchar? Sure. You want to be alpha-numeric? Great. Other than a preference for numeric, is there a reason you want to change the type? I suspect if there is a compelling business case, it will be easier to convince product management to make the enahncement.
Thanks,
Mike
Adqura
TR
Mike,
We didn't change the data type of CustomerID property in Pega Marketing. It is still text /varchar2. All we did so far is to map a numeric Oracle column, unique customer identifier, to inherited out-of-the-box CustomerID. This is working.
We cannot change the data type of existing unique identifer on Oracle/table level because it is already used by other systems, including Chordiant Marketing Director & Decision Management. We were eager to create a new alphanumeric identifier but due to existing indexes and constraints, Oracle DBAs refused to create a new column.
Briefly, as of today, numeric Oracle column is mapped to text CustomerID property in Pega Marketing. We do not know if it's going to break anything. That's why we would like to be able to change its (CustomerID) data type in Pega Marketing...
Regards,
Oğuz