I have just read:
--------- * -----------
Changes Requiring Attention Now
Infor M3 CE October
M3 CE Core: Added limitation to API EXPORTMI & CMS100MI regarding maximum number of retrieved records and changes to the use of selections
The existing toolbox API EXPORTMI and CMS100MI transactions will be limited to a maximum of 10000 retrieved records per transaction. Please note that the recommendation is to retrieve data from Data lake rather than through M3 API.
New transactions or changes to existing CMS100MI transactions using selection fields will use M3 function search as the filtering mechanism. An error message will be displayed to the user indicating if the used main table is not indexed in M3 function search.
EXPORTMI transactions will automatically use M3 function search as the filtering mechanism if used filters do not match an existing M3 database index. An error message will be sent as a reply if the used table is not indexed in M3 function search.
Note For the end user/consumer of the APIs, the input parameters will remain the same and the search query will be automatically generated based on the input parameters.
-------- * ----------
Does anyone know how M3 determines the IDX to use? In EXPORTMI.Select you can only state the physical filename (ex. FPLEDG). Is it based on the WHERE statement fieldnames - read from left to right?
Regards Per Ravnborg
