Hi, I am running SAS version 7.15 HF3. I have an intermittent problem with the import of my infomaps.
Every now and then, an existing instance of all the infomaps in my project will create a new output and not link to the existing output that "feeds" my report. Please see the picture.
This is hard to describe---
Once it breaks, I just have to exit out, which results in lost work.
Any idea to fix this?
Jo
You can relink it to the downstream items. I see you have a Query Builder item -- you can change the properties of the input table in the query (right-click in the query builder on the table name, select Properties) to point to the "new" location.
Most tasks allow you to right-click on the task node in the flow and Change Input Data -- pointing to a different table for input.
But -- it still shouldn't break on its own if you have set the table name. Right-click on each table (new and old) to make sure they seem to be pointing to the same physical table.
The Import Infomaps task allows you to name your output data set (Output data tab). Make sure that you're specifying a name, so that the output always goes to the same location. Then your downstream process should be more reliable.
Hi Chris!
Thanks for responding.
I checked my import and it saves the output to a work file. (see attachment) Is this where I need to change the name?
If I can change this, then I would have to do this on the initial development, correct? Once it breaks, I can't relink the output to what is downstream, can I?
We never experienced this with previous versions of SAS EG. I am tempted to work in the old version of SAS.
Thanks!
You can relink it to the downstream items. I see you have a Query Builder item -- you can change the properties of the input table in the query (right-click in the query builder on the table name, select Properties) to point to the "new" location.
Most tasks allow you to right-click on the task node in the flow and Change Input Data -- pointing to a different table for input.
But -- it still shouldn't break on its own if you have set the table name. Right-click on each table (new and old) to make sure they seem to be pointing to the same physical table.
Thank you, Chris! You are a terrific resource!
My colleague and I tried this and believe it to be a fix to our problem!
I wrote up some directions on how we will try testing this next time it breaks--
SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.