AOW to create relationships between custom modules created with imported data

👨‍💻 Development Help
1

Hi,
We are using Version 7.11.15 and are using it in conjunction with another POS system that synchronises with Suite CRM.

Our data import populates two types of custom modules created in SuiteCRM:

  • Memberships - with details around a membership (due dates, source etc.)
  • Members - with details about each member in the membership (such as price paid, level of membership)

The data synchronisation adds a Membership ID to both the Memberships and Member modules from the POS system. So all Members who relate to a specific Membership will have the same ‘Membership ID’ field as the Membership module.

Can I use a Workflow to set a relationship between related ‘Members’ and ‘Memberships’ using the common (imported freetext) Membership ID field?
Or do I need to do this with code? I’m not very technical, so I’m hoping I can use a scheduled AOW to set it instead of code!

Thanks for any help you can give me, or if you can point me in the right direction for where I should be looking!

2

On reflection, I think I can do this at the time of importing the data by populating the SuiteCRM ID field for the Membership module with the POS Membership ID (because I know it will be unique) and then just link the Member module to the Membership Module using POS Membership ID.
So no workflows required.

3

@NatJP

If I understand your request correctly.

You can use workflow (https://docs.suitecrm.com/user/advanced-modules/workflow/) or logichook before_save (https://docs.suitecrm.com/developer/logic-hooks/) for your ‘child’ module.

But I do this task in 4 steps usually:

  1. Import data of ‘parent’ module.
  2. Exprot loaded records of ‘parent’ module.
  3. Maching ‘ids’ of ‘parent’ module to fields of ‘child’ module using electronic tables (Excel, Openoffice, ect…).
  4. Import data of ‘child’ module.
4

Yes, I’m already doing your 4 steps method to import the historical data from the old CRM, but the new data coming in from the POS system will need to be updated in real time. So I think that if we just set the SuiteCRM ID to be the same as the POS system ID for the parent items, and ensure we update in the correct order (parent, then child) it should be fine.

But thank you for your feedback!

5

@NatJP

I see two variants:

  1. write logichook before_save for child module and make searching id of parent by the name.
  2. write script which using API.
1 Like