Batch Automation Uploads

You can create a mask for unmapped values across every dimension and use the Order to make sure that will be the last rule applied, but it is a VERY BAD IDEA since the whole purpose of a data quality layer is to make sure the whole dataset gets loaded. If your customer has data quality issues and you want to use OneStream to analyze that data you can use a Blend load with Garbage mask rules, allows the users to review the transactions in blend and create a second load with the updated mappings. 

If the source GL data has additional metadata that needs to be created you can include the metadata creation in the connector rule itself so loads will find the appropriate members when loading data. 

We use the TransfromationEventHandler to either add new members under "Unmapped_Members" parent if the we are using one-to-one mapping, or map them to an "Unmapped_Members" base level member if we are using many-to-one mapping. The rule captures the name of the new members that are added and sends an e-mail to the admin to let them know that new members were added. Admin still has to move the new members or update the maps as needed, but at least the load process doesn't fail.