Question
Tata Consultancy Services
IN
Last activity: 16 May 2022 4:10 EDT
Channel Id is not populating in interaction history when we increase the digit length more than 18.
Dear all,
we have customized the channelID in preOfferExecution OTB activity which now more than digit length of 18 but due to this change we the channelD is not populating in interaction history for outbound channels like email,sms,push.
We tried few steps to debug it:
1)I first created a SR property for the channel ID as decimal and also made changes in the Data-Decision-IH-Dimension-Channel table with number , then ran the campaign but it thrown an error stating the precision is 18 in batchout table but the actual value length for channelID is more than 18.
2)I then created a SR property for the Channel ID as text and kept the max length in advanced tab as 50 .we also did change the channelID in Data-Decision-IH-Dimension-Channel Data table as well with text and precision 50.We ran the campaign ,we found that the error while running campaign is gone and also in batch out table the value for channelID is populating and the datatype also changed to text with precision 50 but the channelID was still not populating in Data-Decision-IH-Dimension-Channel table and hence was not populating in the interaction history.
3)I then decreased the channnelID value with digit length less than 18(any random 18 digit value) and ran the campaign again and shockingly it got populated in interaction History and Data-Decision-IH-Dimension-Channel table as well.
Dear all,
we have customized the channelID in preOfferExecution OTB activity which now more than digit length of 18 but due to this change we the channelD is not populating in interaction history for outbound channels like email,sms,push.
We tried few steps to debug it:
1)I first created a SR property for the channel ID as decimal and also made changes in the Data-Decision-IH-Dimension-Channel table with number , then ran the campaign but it thrown an error stating the precision is 18 in batchout table but the actual value length for channelID is more than 18.
2)I then created a SR property for the Channel ID as text and kept the max length in advanced tab as 50 .we also did change the channelID in Data-Decision-IH-Dimension-Channel Data table as well with text and precision 50.We ran the campaign ,we found that the error while running campaign is gone and also in batch out table the value for channelID is populating and the datatype also changed to text with precision 50 but the channelID was still not populating in Data-Decision-IH-Dimension-Channel table and hence was not populating in the interaction history.
3)I then decreased the channnelID value with digit length less than 18(any random 18 digit value) and ran the campaign again and shockingly it got populated in interaction History and Data-Decision-IH-Dimension-Channel table as well.
I am not able to figure out why channelID is working for less than 18 digit length and why not for more than 18 digit length since the data type is now for channelID is text with precision 50 both in pega and in Data-Decision-IH-Dimension-Channel.
Any help is much Appreciated
Pega platform-8.4.3
Pegasystems Inc.
IN
@Ashish Kumar Couple of questions:
What database is being used? Is channelID in the Data-Decision-IH-Dimension-Channel class a new property?
when you say you have changed the precision in the Data Table, was the change done on the RDBMS side or did you set the max length setting on the property?
If you have done the changes only on the RDBMS side, I would recommend saving the DADB Table record for Data-Decision-IH-Dimension-Channel and prior to that set the maxlength property on both the SR property as well as the one in Data-Decision-IH-Dimension-Channel class.
Updated: 16 May 2022 4:02 EDT
Tata Consultancy Services
IN
@RaghuShankhawaramThankyou For the reply.
The database is postgre. No it was not a new property ,we only changed the data type of that property to text in Data-Decision-IH-Dimension-Channel .And the channelId in pega was created in SR and Data- class.
The above practices were already followed. On further investigation I found that when I created a new text property in Data-Decision-IH-Dimension-Channel and In SR class ,and set this new property with the exact same channelId value in preofferExecution OTB data transform, I was again not able to get the channelId value in IH and in Data-Decision-IH-Dimension-Channel as well to this newly created property.
But ,when I tried the same approach by adding volume constraint in multichannel campaign I was not getting the channel Id value in IH in this new property. Is there anything i need to do for this as well? and why the old channelId text proerty was not working?
Pegasystems Inc.
IN
@Ashish Kumar Are you seeing the issue only when using Volume Constraints or does it happen without Volume Constraints applied?
Also, I would recommend raising a customer support ticket as this might need a little involved investigation.
Tata Consultancy Services
IN
@RaghuShankhawaramThis issue is without using volume constraint and with volume constraint as well.
Initially ,when we were running with volume constraint ,we found that 4 values are missing in interaction history i.e channel id, campaign name, pycontext, business value but pycontext and business value got solved when we created the SR property for those with same name/id and data type as of Data- class. But This channelID and campaign name is not coming in IH with volume constraint .But when we run without volume constraint , ChannelID is still not coming after changing it to text but campaign name is populating without volume constraint campaign run.