Yetiforcecrm: [Question] 1:M relations

Created on 20 Mar 2020  ·  6Comments  ·  Source: YetiForceCompany/YetiForceCRM

Hello everybody, I'm struggling trying to implement a 1:M relation.
Suppose I have two modules (this is only an axample to explain my problem): _Car_ and _Parking_. There is a 1:M relation between Car and Parking so that each Car can be in one and only one Parking at a time. Added a 1:M relation with a field in Car module called "Parked in" where I can choose the Parking record. After creating the Car record and assigning the Parking related record, if I go to the Car record dateil view I can see where the car is Parked, but if I go to Parking record I can't see all cars parked there.
Is there a way to have something like tabs for M:M relations also for 1:M relations? Any other way to see the M part of the relation is well accepted.
Thank you in advance

❔ question

Most helpful comment

@zazy
1toM

All 6 comments

All related cars should be visible in Cars tab of Parking record!

image
Запчасти has 1:M field related to IGDN module. If this field filled: record appears in tab.

Thankyou vovpff for your reply but no, there is not such a tab in Parking record. Is there any settings I missed to let it appear? Or simply this doesn't work with "default" modules like Accounts?

This should work everywhere. Activate logs and check what happens when you add 1:M field to Cars module. Maybe this process faulty.

@zazy
1toM

That was the procedure I followed but nothing. Now I have disabled almost all modules, removed all "Cars" records, removed the 1:M relationship, forced cron to run ad added the relationship again and now it works as expected an as you explained above. Don't know what went wrong the firse time. Thank you very much for your support!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rubysown picture rubysown  ·  3Comments

PDMeira picture PDMeira  ·  3Comments

scsikid picture scsikid  ·  3Comments

canomogollon picture canomogollon  ·  3Comments

serbiaserbia picture serbiaserbia  ·  3Comments