Skip to main content

Hello,

I’m working on IFS 24r1, on a IFS 8 > IFS Cloud migration project.

On v8, we have a custom field on Product structure components list which tell us the type of component : purchased, manufactured …

With the Product Structure rework, this CF are not available anymore.
I need to add it, because the bom type reefers to the prodstructure, so the manufactured part, so I got wrong value as you can see, on the component part line, bom type display manufacturing but the component part is a material raw one, purchased, without any product structure.


My issue is I’m not able to recover the entity where I need to add my custom field to read the InventoryPart TypeCode which is the info we want to display here on this list.

If anyone knows, thank you 🕵

Have a good day

Can you add an expression custom attribute to the ProdStructure Entity/LU?
ifsapp.inventory_part_api.get_lead_time_code(contract,part_no)


 

Can you add an expression custom attribute to the ProdStructure Entity/LU?
ifsapp.inventory_part_api.get_lead_time_code(contract,part_no)


 


I found the issue, but I can’t explain how it happens, and how to resolve it.
ProdStructure entity doesn’t exists on my development environment (to do the porting from v8 to cloud about custom events, custom fields etc ...), but it exists on my production environment (used for dry run before the GO LIVE).

 

dev env




 

prod env


But there is no issue when using the app with product structure on the dev environment.
We still have prod_structure, prod_structure_api, prod_structure_tab, prod_structure_cft but no prod_structure_cfv or prod_structure_cfp on dev environment.

Also, the ProdStructure entity is not referenced in the Informations System > Entities page.

That’s really weird

If you click + in Entity Configuration and you add ProdStructure, does it work or do you get an error message?  If you get an error message, which one?

 

I’m on 25r1 and I have ProdStructure present without issue in the Entity Config, so you might want to raise an IFS ticket if it’s not there for you as this doesn’t seem very normal

Found the issue, was a wrong module metadata comment value on a custom package, which is used by the dictionary cache system 

Terms & ConditionsCookie settingsAccessibility statement