Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

DataPrep Export element fails

Hi,

I've faced an issue in various situations where the DataPrep Export element may crash if the source file is missing. I'd like the process to complete normally even if the source file isn't present.

I've noticed that the DataPrep Export element only fails when a specific Load Plan is selected. In a sample case below, the element doesn't fail with 'Detail' or 'Sort' but if 'GroupBy' is selected, the element fails. I don't understand why this happens.

I'm asking if anyone has an idea of how to avoid this issue? So far, I've been working around the issue with the Api.GoToItem method (which my previous question was about), but that's not an option for the process I'm developing. I don't know if the fix in version 2025.0 below is related to this? We are still using version 2024.1.

"Detail" or "Sort" selected:

"GroupBy" selected:

Export_issue_test_workspace.zip

Any help would be greatly appreciated!

-Lasse

Find more posts tagged with

Monarch Server

Accepted answers

All comments

Nicholas_21406

Hi @Lasse,

Thank you for attaching your workspace - could you also attach your visual process and the input file?

Lasse

Hi @Nicholas_21406 ,

Thank you for your reply. Sure, please see the attachments.

Test_export_issue.zip

Test_input_file.txt

Nicholas_21406

Thank you for sending your Visual Process and input file.

I can confirm it runs without errors for me in Automator 2025, even when I select the Group By Load Plan - my colleague is going to try it on Automator 2024 to see whether it fails there.

Regarding "…DataPrep Export element may crash if the source file is missing," can you say what behavior you would like to see if DataPrep Export does not have an input file? You will get a similar error using DataPrep Studio if the input file is missing.

Nicholas_21406

My colleague has confirmed he is able to export the GroupBy load plan (and also "All Load Plans") when running your visual process on Automator 2024.1.

Perhaps you could send a screenshot of the error you see when your input file is found and you attempt to export the GroupBy load plan?

Lasse

I think I explained the issue a bit poorly. The issue occurs when there is no file in the folder (File Input element). When either Detail or Sort is selected in the DataPrep Export component, the component is skipped. However, when SortBy is selected in the DataPrep Export component, it fails with the error "Cannot open the file...". I would like the DataPrep Export component to be skipped when SortBy is selected.

If there is a file in the folder, the process runs well.

Nicholas_21406

Hi @Lasse, may I assume that when you refer to "SortBy" you meant to say "GroupBy"?

At least on Automator 2025.0, I see the same behavior when the "Detail" Load plan is selected in the DataPrep Export node:

versus when the "GroupBy" load plan is selected:

Is this not the behavior you are seeing? I can ask my colleague to try the same test on Automator 2024.1.

Lasse

Hi @Nicholas_21406 , thanks again for testing!

Yes, I meant to say "GroupBy", not "SortBy".

I'm seeing a different behavior than you.

When "Detail" is selected, the DataPrep Export doesn't fail:

But when "GroupBy" is selected, DataPrep Export fails:

It would be great if your colleague could test this on Automator 2024.1. 😊

Nicholas_21406

Thanks @Lasse ,

Ok I have asked my colleague to try this out with Automator 2024.1. It is also interesting that those two warning messages you are getting "No inputs found for location…test*.txt" are different than the one warning message that I am getting "File '\WIN-Q144OJ4PNAO\C$\scratch\community\196104\Test_input_file.txt' not found.".

The way I "moved" the input file out of the way was just to rename it to Test_input_filex.txt. Was the input directory for you completely empty?

Lasse

Thanks for asking your colleague to try!

Yes, the "Testi"-folder is completely empty when I'm running the process.

CPorthouse

The behavior you are describing is mostly by design. I believe you have two options if you would like the process to continue if you are missing the input file. You can either enable "Show advanced connectors" and then use the error execution flow on your export to continue to the next node.

The other option would be to use the "Verify Workspace" node to make sure you have at least one row in your detail load plan before continuing to process the GroupBy node.

Lasse

Thank you @CPorthouse for your comments!

I'm afraid neither of those suggestions will work for my case. I want the components that come after the DataPrep Export component to also be executed. In this example case below there are just one component after the export, "Sript2". And as we can see this script is not being executed.

After the Verify Workspace component, the process seems to be following both the gray and red paths. I think it should follow just the red path as there are no input files. I suspect this isn't working as planned, am I correct?

CPorthouse

I think the problem you are running into is going to be related to your other question. Your script 2 node has two inputs so it is waiting for both of the previous nodes (DataPrep Export and Script) to complete before executing. The script node shouldn't run if the verification passes.

I suppose you could create a sub-process that gets called from DataPrep Export or the Script node separately.

This way you can run the next node/process without waiting for the previous 2 nodes to complete.

Lasse

Thank you for your suggestion 😊 I'm not so familiar with the Verify Workspace element. May I ask which path (gray or red ) does the process follows after the Verify Workspace element when there are no inputs? And when the settings are as below: