Custom Projection Entity Associations Not Showing Custom Fields

if you find  a solution to this i would love to hear it. I can’t see my Custom Fields on the standard entity in the pagedesigner from a custom Projection.  

Could you please verify whether your fields are available in the “Additional View” of the entity configuration?

Depending on your page setup, you might be using a different view instead of the standard one.

Thanks for the suggestion. The view that was being used from looking at the diagnostic information is the root view. All additional views for this LU are Approved and published as a last resort effort when testing so had similar thoughts as your recommendation. The additional view is something we are familiar with it would be nice if the interface could clue the user into these type of settings issue as even knowing it is hard to track down which one is being used.

This issue is still outstanding and currently have not viable path to work around the issue.

yes. 
I have the Same issue. 

I have added a standard Entity (InventoryPartInStock) to the Standard Projection for InventoryPart. 

and i can see the InventoryPartInStock entity in the Page im modifying. 
 

the InventoryPartInStock entity have two CustomFields Remnants_on_hands and Difference. 
 

these two custom Fields i cannot see in the page designer:
 

when looking at the Entity views i can Clearly see the Fields. in the Standard CFV field.

But the page designer/the API does not seem use the INVENTORY_PART_IN_STOCK_CFV view. It seems to use the INVENTORY_PART_IN_STOCK (Base)
eventho the Page info says that the view is the CFV 

When looking into the API documentation i cannot see the custom Fields either.
Is there any thing that needs to be refreshed? some kind of server cashe.

Or is it simply imposible to see custom fields from 2 different Entities in the same Page/projection?

MSBavngaard,

What you’ve described appears to be a different issue. We have encountered something similar within the Inventory Part In Stock LU. If I recall correctly, the limitation exists because this LU is largely computed, which restricts extensibility through page configuration in the way the page was originally designed. I believe we received clarification from IFS on this a couple of years ago, and I can try to locate that response if it would be helpful.

The issue I am currently working through involves creating a custom LU and establishing a relationship to another LU via a custom projection, while also enabling custom fields to be displayed on the connected LU. Based on several test scenarios, the design appears to be either limited or not functioning as expected, which differs from what I had initially hoped to achieve. The hope with the post was to get confirmation of the limitation or a possible workaround.

Hej Jsham.

Yes i see this is slightly different.
I try to access a Custom Field on a Standard Entity on a Projection. 
I have the same issue when looking in the projection as you have. 

I have a Theory that Custum fields on a Entity just never show up on a Assosiated Entity in a projection. and that it’s just a Limitation in IFS. that shure is not intentet.