How to avoid: Error ==> Parameter Source for '<Enter List of X>' did not return any data
K
Kirc Breden
started a topic
1 day ago
Ever have an expected Burst that fails without really being a failure?
Particularly, the error you might expect, (Error ==> Parameter Source for '<Enter List of X>' did not return any data)
We all know if it had data to run, it would run flawlessly, but for many days out of the month, we expect there is no data to feed that Burst.
Here is how you can prevent that scenario with Conditional Delivery:
Lets say, you have a Burst (Burst B), that uses a list values supplied by a previous Burst (Burst A), that generates the List.
When Burst A runs, it distributes an .xlsx file that supplies the FileList (File List A) which is used for Burst B.
Simply, create a second distribution of the same file generated, as a different named file, (Trigger.xlsx) then, set that distributed file with a Delivery Condition
In My case: (Worksheet: Report 1 | Cell: A2 | Condition: >=1) (but you can identify any number of conditons to test for)
This will result in 1 of 2 results, the file gets generated when the condition is met, or no file is created in the network folder location you want to drop the file in.
Set Burst B, to run from a schedule (Schedule B) and make an event trigger to look for the file you may or may not drop.
Set the schedule to be 'event only' to fire off.
What is left, is that Burst A will run successfully, may or may not have data to fill the File List, but will only drop the trigger file, if there is data to run Burst B.
Kirc Breden
Ever have an expected Burst that fails without really being a failure?
Particularly, the error you might expect, (Error ==> Parameter Source for '<Enter List of X>' did not return any data)
Here is how you can prevent that scenario with Conditional Delivery: