Custom Guided Wizard

introduction breadwinner was designed to create transactions (payments, subscriptions, and invoices) from accounts or contacts without any configuration however, you may wish to create transactions from other objects, perhaps an isv app or your own custom objects there is virtually no restriction to how you might approach this, other than that the transaction must be linked to an account or contact (through either a formula or lookup) and the record the transaction originates from restrictions a surprisingly common request is to populate fields that do not exist in the payment processor for obvious reasons, we cannot populate fields that don’t exist you cannot pull data from two or more fields into a single field, but you can achieve this by using a formula field that concatenates those two fields this is why we strongly recommend you pull data from formula fields (compared to user populated fields) formula fields have the advantage of combining two or more fields, pulling data from parent records, or using logic to populate different information based on other fields preparation the breadwinner payments object (typically either the invoice, subscription, or transaction) must have a lookup to the originating object for instance, if you are creating an invoice from orders, you will need to create a lookup field in the bwp invoice object in salesforce to the order object and we strongly recommend you add the relevant related list to that object’s page layout the originating object will need either a direct lookup to an account or contact (either via a lookup or master/detail) or a formula field of the salesforce account or contact you wish the transactions to be created under