Hi @CU10121822-0 ,
Please have a look into the article shared by Syed, it is given in detail when to use skip staging when not, from front-end directly it will be difficult to identify the entities that supports export without staging.
Sharing the extract from the article for your easy reference:
"
Avoid implementing postLoad when possible
Don't implement postLoad, because it forces the export to go through staging.
Entity authors can implement many methods on data entities to customize what happens when those entities are used. One method that you should avoid using is postLoad. This method requires that your export data is copied into your staging table, so that the method can be called once for each row. Afterward, you must copy the data from the staging table to your destination database or file. It's inefficient to copy all the data a second time. In addition, for full exports, the size of the staging table quickly grows over time. As a result, insert, update, and select operations on the staging table become slower.
If there are values that you want to change before export, consider using a computed column formula to return the modified value. If values must be set just before import into the entity, consider using postStaging. In addition, the entity's insert and update methods can be customized to modify values for specific columns. Any of these alternative approaches let you skip staging for your export.
When you create an export project in the user interface (UI), don't set up your export to use staging unless the entity has a postLoad method or a virtual field (that is, a value that's computed by an X++ method), or unless it must export bitmaps. Export through staging requires that the data is exported two times: once to the staging table and once to your destination. Therefore, use this approach only if you must export something that can only run in the staging process.
If any columns in your entity are linked to configuration keys that are disabled, and you select any of the disabled columns, export fails unless you use staging for it. If your entity only works if you export through staging, check for fields that have configuration keys. In addition, because the configuration key settings are often on the enumeration (enum) object or extended data type (EDT) instead of the table or data entity view field, check for configuration keys on enums and EDTs too. If any fields, enums, and EDTs have configuration keys, don't export through staging. Instead, remove the mappings for all the disabled columns, so that you can skip staging. This approach is faster than going through staging."
Regards,
Neeraj Kumar
