Hi, Unfortunately the baseline mass_update does not support inserts indeed. Its always a bit tricky to get around this through configuration. For several customers we are using a “generic” custom MPM for supporting mass_insert of which you can see an example below. <perform_mass_insert> <parameters> <select> <hierarchy_select> <primary_table>person</primary_table> <attrs> <attr>person.person_id</attr> </attrs> <from> <table>person</table> </from> <where /> </hierarchy_select> </select> <update> <update_person_event> <person_event> <person_id xpath="person_id"></person_id> <event_type>NOTIFY</event_type> <insert_update is_initialized="False" /> </person_event> </update_pe
Hi @Rwjgoedhart , another option could be a combination of update and insert. Use an user_def YOR field on the person. If a new place has been created, the hierarchial select will identify the person which needs to be updated. Then create an insert for every person which has been updated. This can also be done over night via a scheduled process. To make it very clear, you can create another update at the end based on the hierarchial select to clear the YOR field. I did this very often due the mass insert limitation. Hope this helps. Best regards, Sven I have been noticing some inconsistent behaviour with this method at a client on 6u7. Code that was working in 6u3 and 6u5, is now intermittent.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.