Question

IFS10 How do you make a native field required?

  • 9 January 2023
  • 4 replies
  • 173 views

Userlevel 1
Badge +4

IFS10 How do you make a native field required?


4 replies

Userlevel 7
Badge +21

Hi @bverdera ,

 

We define a field as required or mandatory in the object properties of the screen.  If we’re using the IFS Enterprise Explorer (IEE) user interface we make sure we activate the base profile we wish to put the mandatory field then we go to the screen such as Inventory Part.  On the screen we would RMB and choose properties then click on the Mandatory tab.  We would then check the field(s) we wish to make mandatory.  Once we’ve checked all the fields we would press the Apply button and save our base profile.  Now when someone who is assigned to that base profile logs into IFS and tries to create a new inventory part they’d be required to enter information into those fields we made mandatory.

 

 

If you are using the IFS Aurena user interface you would navigate to the screen you wished to make fields mandatory then open the Page Designer and select the context you wished the change to be enforced.  By default IFS will select the global context.  After you make the change you’ll need to save and publish the change.

 

 

 

 

Regards,

William Klotz

Userlevel 1
Badge +4

Thanks William, yes, we did that and somehow empty ones are sending to our other applications blank.  We have made the adjustment for the profile that would be responsible for that field.  I guess we will have to do it for all profiles.  This isn’t a custom field either.  We don’t use Aurena.

Userlevel 7
Badge +21

@bverdera ,

 

You are correct in that you’ll need to perform the settings for each of your base profiles if you wish everyone to have the field mandatory.  IFS Aurena is similar in that if you define contexts other than global you’d have to perform the settings for each of the contexts.

 

Regards,

William Klotz

Userlevel 3
Badge +7

IFS10 How do you make a native field required?

The answer above is correct but do ensure to consider that native fields - when made mandatory on a screen, are not necessarily mandatory in assistants. 

For example, you can make product code mandatory in the screen, but that will not force this on the new part assistant. It will, however, make it mandatory for any changes made in the screen after.

(Image below shows product code mandatory on screen, but not assistant)

So you may need to consider if the use of any assistants you have is the right thing for your business.

Reply