search

YetiForceCompany / YetiForceCRM

Our team created for you one of the most innovative CRM systems that supports mainly business processes and allows for customization according to your needs. Be ahead of your competition and implement YetiForce!
https://yetiforce.com
Other
1.74k stars 750 forks source link

[bug] Mapping has bug #10185

Closed waran70 closed 4 years ago

waran70 commented 5 years ago
  1. Custom module with field 1:M (Accounts) - custom module have multiple 1:M fields with different names and labels.
  2. Payments in module with custom field 1:M (Accounts) Both fields have the same name and label. Set mapping to those fields but it is never paired as expected. System chose always one field 1:M but not the one that was mapped. It is obviously some bug as the designation of mapping function is invalidated
waran70 commented 5 years ago

I need to add that it works IF the other field is empty. It means that Yetiforce prioritizing probably the first 1:M field created in the custom module.

bpabiszczak commented 5 years ago

Are there two fields 1: M [in one module] pointing to the same module ?