6
In D365 F&O, when we do CDS integration through Plower Plateform, there is a time limit of 5 min execution of first 100 records to fetch from D365 F&O. it gets fail many time due to the reason behind is staging table of data entity. Source data is getting filled to staging first then target. Staging is by default involved due to some product limitations like if Memo/container/virtual fields are available in entity, if PostLoad Method is available in entity, if entity is composite. these conditions are in DMF source code. So getting followed for CDS as well. where as on other side we have option of skip staging for manual DMF export and import.

Idea is , there must be a change on these limitation. for CDS (data integrator), no matter if any custom logic is written on PostLoad method or not, if any Memo/container/virtual fields is there in entity or not. For any case it should NOT go to staging, at-least for transactional tables where data might be high and possibility of request timeout is more for CDS.
Category: General
STATUS DETAILS
Declined