Best practice for making IEA Upload Filters for Safran

Modified on Thu, 22 May at 1:32 PM

TABLE OF CONTENTS


Introduction

This article will show you the best practice for making (complex) filters for uploading data from Safran to IDE. The concept is to use a calculated flag-field in Safran (e.g Flag8), where all the complexities of the filter is hidden from the user - resulting in the filter for both Safran and IDE being very simple (here for IDE): "uf_flag8 == True".


It is recommended to use this practice if your filter contains more than 2 fields.

The advantage of this practice is two-fold:

1. You will have a filter in Safran that will guarantee to produce the same result in IDE.

2. It can be used within Safran between multiple users as well as by IDE.


How to set up a calculated flag field in Safran

Step1

We will in this example use Flag8 (See screenshot below where "L8" represents flag-field #8, and where we have given it "Export to API" as the Label (display text):
A screenshot of a computer

Description automatically generated


Ensure that you have checked the "Calculate Value" option, as well as the "Save To Database" option.
Press the "Formula..."-button.

Step2

Press the "Filter..."-button seen below: 

A screenshot of a computer

Description automatically generated


Step3

Define the filter according to the documentation in Safran (a complex example is shown below that would have been quite challenging to recreate in IDE and to ensure the same result!):

A screenshot of a computer

Description automatically generated


Press "OK".


Step4

Press the "Formula..."-button seen below:

A screenshot of a computer

Description automatically generated


Step5

Set "1" as the expression, as seen below:

A screenshot of a computer

Description automatically generated


Press "OK".


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article