Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You seem to be trying to create an Address record directly, bypassing the two already created for the Contact record by default (it always creates these two records, whether or not you use them and whether or not you want the "shadow" fields from them to be visible in the Contact form). You say nothing happens - is that verified by looking in the SQL tables or at the "More Addresses" link in the Contact record?</p> <p>One thing you seem to have omitted from the create is specifying the address number (and ideally doing this by first finding the largest number on all addresses already associated to the Contact and incrementing by 1). This would need to be at least 3 in all cases.</p> <p>If you look at the Address entity Associated View definition you will see that it explicitly filters to include addresses where address number > 2 in order to provide the illusion that 1 and 2 are "part of" the Contact and the "more" are separate records, whereas in fact all addresses including 1 and 2 are rows in the address entity table in their own right.</p> <p>So I suspect that if the value is left as null, the address simply won't show up in the GUI as it does not meet the filter criteria. It may or may not also fail to create as it relies on that field quite heavily internally so I would treat it as "system required" and make sure to include it in the column collection.</p> <p><strong>Alternative approach:</strong></p> <p>If you are never using the fields for Add_1 or Add_2 on the form, you could still use the Address record with address number 2 to store your data from the Lead, making it an update of this existing (empty) record rather than a create. </p> <p>Modify the Address Associated view to change the filter so it will include Add_2 in the view, by making it filter for address number > 1 instead of 2.</p> <p>This will appear to users like there is one address there already and they can add more with normal functionality for address_3, 4 etc (which they might consider to be 2, 3 etc). Address 1 exists but is empty and can be ignored.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload