About pcapazzi

pcapazzi · ‎06-16-2017

Thanks! You got me going in the right direction. I am able to get details of the current information map and can store it and compare when changes I request are made. /* proc infomaps metauser="user id" metapass="password" metaserver="server" metaport=8561; update infomap mapname mappath="/path to where the map is located/" verify=no; **don't verify sources list _all_; **list everything */ This shows the results in a log. There is an XML export function which I can explore. But what I really was happy to see was using proc sql worked out as expected: libname mymaps infomaps metauser=userid metapass=password metaserver="server" metaport=8561 mappath="/path to infomap/"; proc datasets lib=mymaps; **libname for this path run; quit; option validvarname=any; **case insensitive proc contents data=mymaps.mapname; **put in the campaign map name run; proc sql ; **run a query against a data item and compare results to your source. select count(*) from mymaps.CampaignMap where 'Postal Cd'n='33065'; **for field names with spaces enclose them in single quotes with an n afterwards. Worked like a charm!

pcapazzi · ‎06-16-2017

Is it possible to query the Information Map with PROC SQL? I'd like to have a script where I can verify a field has been added and query it to ensure the relationship is set right or that there are no unexpected duplicates in other tables.

pcapazzi · ‎06-12-2017

There is no need to drop and recreate a Communication Node to change an Export Definition. You would need to drop and (re)add the Export Definition within the existing Communication Node. I think your point is that you do not want to update the Communication Node in all 500+/- campaign diagrams you have which is understandable. I am not aware of a way to automatically update the Export Definition in a given list of diagrams. I think the closest you can come to managing the Export Def for several campaigns would be to have one diagram that simply exports the data using an Export node instead of the campaign diagram. This would be a complicated set up though as you would have to make the export diagram smart enough to export a given campaign diagrams data. Or perhaps you could have this one diagram export the results of all campaigns run during the previous day (all subjects with contact_dt of yesterday in contact history and perhaps a list of campaigns in a given folder name or specified list of campaign codes). That's the best I could come up with. Good luck.

pcapazzi · ‎06-09-2017

Thank you. I heard back from our IT who had said they are populating the field I was inquiring about with the counts of agents at the point where we re-publish reporting data and that previously the field was not populated by CIS. Thanks!

pcapazzi · ‎06-09-2017

We have a process where we return to a campaign and update a campaign level attribute and then re-publish the campaign without executing it. This is so that an external process can be kicked off. However, in reconciling counts between our initial reports and counts in the CDM weeks after the execution there is a discrepancy. Over time there are subjects that will be removed from the tables CIS works with. However... I think that when we re-publish a campaign weeks after execution (and we do not re-execute) that the CI CELL PACKAGE table may be getting updated counts at that time. Is this a valid assumption? If it is valid is it updating counts from the contact history table or from the infomap? Note: out contact history table is updated weekly to remove invalid agents. The same is done to the underlying tables that the infomap uses. Example: Campaign 1 has a single segment. There were 100,000 subjects at run-time and 100,000 customer were mailed. After the mailing has gone out we revisit the campaign (say 1 month has passed) to set a variable that the campaign is 'done' and we hit publish reporting data. Another month passes and we are reviewing the counts and see that CI CELL PACKAGE has a TOTAL_MARKETING_CONTACT_CNT of 99,998. We are using CIS 6.4 Thanks.

pcapazzi · ‎05-26-2017

Not by a calculated item immediately. In the communication node you could export to a table that would need to be available in the information map. The table could be as simple as Subject_ID, Tracking Code, Treatment Tracking Code. You could then add a calculated concatenated item of those two fields. The Communication node can be thought of as a "checkpoint". Once the Communication node has executed the data will be in that table for use in subsequent export node. You would then use an export node afterwards that would produce your XML file with the concatenated field. You may also need a Cell between the Communication node and the Export node. Note: If your XML export uses other fields from the communication node that you don't see available in calculated items (ex: package code) you may need to use a Cell -> Select (contact history campaign code and possibly occurrence no if recurring) -> Export (with Refine set to results of Select node). We have to do this in our campaigns. However, if you're building the export above you could throw in more fields than the two mentioned for concatenating and avoid this set of extra steps. ex: If you were using Package Code in the export add Package Code to the Communication Nodes export and make it exposed as well in the infomap. Hope that helps!

pcapazzi · ‎05-24-2017

I just noticed in your first attachment that there are zero subjects in your campaign. Try it with some subjects and the Process node at the end may work out then because it has something to work with. Put another way, it may be that the code behind the Process Node does not have error trapping for the case when there are 0 subjects and needs subjects in order to complete without error. I wouldn't suggest changing the code or stored process configuration to ignore the parameters until you are sure you still get errors when you have subjects processed. You also say your campaign ran fine. Do you mean the expected results of the process node is correct? Give some detail around why you say it ran fine...

pcapazzi · ‎05-23-2017

Can you tell me more about these? COMM_CATG EMAIL_ID COMM_STDT COMM_TIME OFFER_ID CLI_ID Are they parameters for a stored process in the process node? Does the Stored Process have Prompts set up properly? Or if it's code pasted directly into the process node how are you assigning the values?

pcapazzi · ‎05-23-2017

In the process node there should be a Log tab. Scroll through the log and look for a line that starts with Error". Post what you can around that part.

pcapazzi · ‎05-18-2017

If you add nother communicatinon node to the same diagram does the same thing happen? Is the diagram in read-only mode? Is this the only digagram where you have this issue? Is there another session that has a lock on the diagram? Do you have another session open? I'm not an admin but there are user levels. Check with your admin about how you are set up.

pcapazzi · ‎02-28-2017

I think it's possible... though I don't have the permissions to create a test. 1) I went to the SharePoint Site I would like to upload files to 2) I clicked on the Library tab at the top and then clicked on Open In Explorer from the ribbon 3) I noted the network location and converted it to a URI (remove http:// and use \\ and \'s between folders). 4) I used the URI created and tested a create and delete file with success Next steps are what I would attempt but do not have access to test 5) Create a CIFS or SMB share from linux with proper write permissions (Or perhaps SAS can work with a URI? The SAS Service Account would need write permissions) 6) Make that path available to SAS CIS Great question as this may be an option for us to look into to improve our workflow. Best of luck.

pcapazzi · ‎02-13-2017

We copied a production diagram into a different business context on the same server the we use for testing purposes. The CAMP code was never changed and the diagram has been deleted. We would like to bring it back to change the CAMP code so that reporting based on the CDM does not show duplicate records. Thanks,

pcapazzi · ‎01-13-2017

Hello, MOMA appears to be a very manual process. We have to update counts in the campaign diagram, generate input data from a campaign group, optimize the scenario, execute the group, and then execute the individual campaign diagram. Each of these components take some time so a person has to monitor the progress of each setp. Assuming the scores are ready for use, the scenario has been marked as preferred, and the campaign diagram and group are set up... how can you execute these components by a schedule and/or trigger? Also assume for the time being only one campaign diagram in the campaign group. Thanks.

pcapazzi · ‎12-19-2016

Does the data source actually have 100 records or is the 100 record count you see from metadata that may be stale where the table has been emptied since the last time metadata was generated? ##- Please type your reply above this line. Simple formatting, no attachments. -##

pcapazzi · ‎09-30-2016

What is the definition of the constraint?

Online Status	Offline
Date Last Visited	‎07-20-2018 09:47 AM

Re: How to verify the "Map node" results in SAS EG

Re: Querying next runs of campaigns

Re: Querying next runs of campaigns

Querying next run of campaigns

Re: Error in Export node while executing the campaign in new server

Re: Error in the stored process

Re: Error in the stored process

Re: How to add a new communication channel code in SAS CI studio

Re: How to add a new communication channel code in SAS CI studio

Re: Include the Excluded

Re: How to add a new communication channel code in SAS CI studio

Re: SAS CI - error in communication node

Re: mabatch.sh help

Re: How to populate CI_RESPONSE_HISTORY with ETL?

Re: Using dynamic treatments in SAS CI

Re: Can the Information Map for CI Studio be appended to by a process?

Re: Include the Excluded

Re: How to find changes done to a particular campaign by a user in CI ...

Re: mabatch.sh help

Re: How to execute a campaign in future date

Re: Can you query the Information Map

Can you query the Information Map

Re: Change Massive Export Definition Variable Format to Old Active Cam...

Re: CDM - CI CELL PAKCAGE counts changed slightly

CDM - CI CELL PAKCAGE counts changed slightly

Re: Combine default CI export fields

Re: after executing the campaign it is throwing the below error

Re: after executing the campaign it is throwing the below error

Re: after executing the campaign it is throwing the below error

Re: options disable in while creating designer tab in communication no...

Re: SAS CI to Sharepoint

Can a campaign diagram be "undeleted"?

MOMA - Automated Execution

Re: Split node issue in SAS Customer Intelligence Studio

Re: Managing Common Data Model