List of ALL Mandatory Fields and Tabs

Hi ​@Vernon Anderson,

Mandatory field per record type information is already available in the Entity screen.

Please refer to the screenshot below, Required Flag field lists out all mandatory fields required for an Inventory Part creation. e.g., Contract(Site) is a mandatory field and it is only insertable, not updatable. 

Hope I understood your requirement correctly.

Regards

Abdul Rehman

Abdul wrote:

Hi ​@Vernon Anderson,

Mandatory field per record type information is already available in the Entity screen.

Please refer to the screenshot below, Required Flag field lists out all mandatory fields required for an Inventory Part creation. e.g., Contract(Site) is a mandatory field and it is only insertable, not updatable. 

Hope I understood your requirement correctly.

 

Regards

Abdul Rehman

A quick addition Abdul, in some cases SOME fields may be mandatory with a Required Flag not set if the requiredness is conditional and handled through business logic, typically through RnD Core Overrides.

For instance, INVOICE_RECIPIENT in IDENTITY_INVOICE_INFO is not marked as a Mandatory Field at entity level, but would be considered mandatory if the Supplier Invoice Workflow component is installed:

SimonTestard wrote:

Abdul wrote:

Hi ​@Vernon Anderson,

Mandatory field per record type information is already available in the Entity screen.

Please refer to the screenshot below, Required Flag field lists out all mandatory fields required for an Inventory Part creation. e.g., Contract(Site) is a mandatory field and it is only insertable, not updatable. 

Hope I understood your requirement correctly.

 

Regards

Abdul Rehman

 

A quick addition Abdul, in some cases SOME fields may be mandatory with a Required Flag not set if the requiredness is conditional and handled through business logic, typically through RnD Core Overrides.

 

For instance, INVOICE_RECIPIENT in IDENTITY_INVOICE_INFO is not marked as a Mandatory Field at entity level, but would be considered mandatory if the Supplier Invoice Workflow component is installed:

 

 

 

​@SimonTestard Yes you are correct. Conditional fields are not considered for Required Flag.

Anyways, Entity screen can be use to get high level information regarding mandatory fields.

This is a very good start but to me the problem is also the interlinking of the tables. 
So imagine starting with an empty database, what is the ORDER of migrating your data in. 

To me the idea of saying, “I want to be able to create a customer order for client x” entails a lot of work before you can even start. But how do I know “what” work needs to be done? 

How I approached this, but never really succeeded is trying to do the following:
 

• What are the required fields on the entity (thanks ​@SimonTestard  for your tip as I was not aware of that and it makes why my theory sometimes falls down) 
• Then trace back/down in the full tree of dependencies what tables are involved using the default base views and the references to other entities (if defined correctly in the entity metadata?)

Eg. 

 

So in my theory for each field which is mandatory check if there is a reference linked and check that this view is setup already or not. 

Somehow you can define the base view each setup has (like IsoCurrency / IsoCountry) etc. 
But in the end it would be great to be able to search or check easily what view to fill in and then in this case in which order? 

So can we build up a list of “views” which are level 0 (like all the ISOxxxx views) then views which are level 1 etc etc. But now I do not know, should I first load the site or first load the CustOrdCustomer view?

Would there be an extra ideas here about this as data migration and setup is the most painfull part of IFS and understanding it is sometimes hard! 

So feel free to share your ideas about how we can maybe build some sort of an annotated data dictionary for IFS with an easy way of showing the order you have to load etc. 

Curious about your thoughts on this! 
 

To be honest on any migration I’ve done so far, I’ve always had to create the sequencing itself within a block manually.

So for instance, for customers:

For actual Basic Data Requirements though, typically this is handled through the Scope Tool to list every type of basic data you may need to have filled out in a Basic Data Tracker in order to properly use a module, but not everyone necessarily has access to those as Scope Tool is very customer centric on purpose (the output being customized based on which modules are part of your individual solution etc.)

If you’re doing it manually, like I have, I basically check up in the entities in the tracker above any column that has a REF comment, and that tells me which referenced entities I need to be sure are loaded first. It’ll either be basic data or parent data.

So for instance Customer ID in CustomerInfoAddress is linked to Customer ID in CustomerInfo (which is its parent), so obviously that informs your “inner” sequencing of loading a complete customer.

Corporate_Form in CustomerInfo however is a referenced field to Basic Data, so that informs your “outer” sequencing, letting you know you need to make sure that basic data is loaded before you migrate.

I don’t really know if there is a public document that anyone has ever compiled that keeps an up to date version of that with clear, solid sequencing rules. A lot of Partners have their migration team create such documents, but obviously that becomes “billable” work product and so they’d likely be reluctant to share that freely.