We are using the default load methodology ( not using load rules) in our load action. The issue is when there is a rejected record ( e.g. an invalid member or something), the process logs that record and it stops there and fails.
We want to see if there is a setting or something where the process logs these rejected records and continues loading rest of records ( similar to the Load Rule behavior)
With Essbase when a load is done and any record in the load fails, it will not load the entire recordset in the file. In order to load successfully all intersections in each record in the .dat file must be valid for load or it will fail.