Plan, execute, measure and optimize customer experiences

SAS Customer Intelligence studio Communication node Custom details selection list

Accepted Solution Solved
Reply
New Contributor
Posts: 4
Accepted Solution

SAS Customer Intelligence studio Communication node Custom details selection list

[ Edited ]

Hi,

 

I am facing issue with custom detail in  Communication node where one selection list select the list of templets defined in Common data model table.

 

Problem is while selection it is taking too much time( around 2-3 minutes ) and some times generating error.

 

Is there any solution for this ? how to speed up  and get quick selection value after clicking on list box.

 

Attachement shows the list slection where delayed.

 

Br,

Mrityunjay Kumar

Attachment

Accepted Solutions
Solution
‎02-13-2017 07:10 AM
SAS Employee
Posts: 70

Re: SAS Customer Intelligence studio Communication node Custom details selection list

We've encountered that behavior in the past, especially when the table used to populate the list comes from a database. The delay is the time it's taking to connect to the database, since it doesn't maintain a connection behind the scenes, and in some environments on some databases that can take time to establish.

 

As a general practice, I advise my team to use SAS datasets for lists like that specifically to avoid this issue. Most of the time these lists are pretty static, so they can be created and maintained in EG, for example. If they really are data driven from a database, then a recurring ETL job to keep the dataset current is the easiest way to decouple the list from the database connection.

View solution in original post


All Replies
Solution
‎02-13-2017 07:10 AM
SAS Employee
Posts: 70

Re: SAS Customer Intelligence studio Communication node Custom details selection list

We've encountered that behavior in the past, especially when the table used to populate the list comes from a database. The delay is the time it's taking to connect to the database, since it doesn't maintain a connection behind the scenes, and in some environments on some databases that can take time to establish.

 

As a general practice, I advise my team to use SAS datasets for lists like that specifically to avoid this issue. Most of the time these lists are pretty static, so they can be created and maintained in EG, for example. If they really are data driven from a database, then a recurring ETL job to keep the dataset current is the easiest way to decouple the list from the database connection.

☑ This topic is SOLVED.

Need further help from the community? Please ask a new question.

Discussion stats
  • 1 reply
  • 193 views
  • 1 like
  • 2 in conversation