Use of Flows and Validation Rules with Breadwinner

flows to the accounting system (e g , automatic invoicing) due to limitations with salesforce, you cannot use flows with breadwinner when breadwinner requests data from accounting/payment systems, it gets multiple records in response and, when it creates or updates this data into salesforce, it uses salesforce's bulk api specifically, salesforce requires breadwinner (and all appexchange apps) to load data using the bulk api if you need automations or other functionality typically achieved with flows, you can explore the apex based breadwinner global api flows from breadwinner objects inside salesforce it is possible to create flows that originate on breadwinner objects and update other salesforce objects validation rules we strongly recommend that you avoid using validation rules on the invoice object you may, of course, choose to do this, but if you do, we are unable to support you, and we expect this to likely cause fundamental issues with breadwinner and result in incomplete data this may seem strange at first, as validation is so common in salesforce however, breadwinner only stores information in the invoice object after retrieving it from your accounting system when someone clicks the new invoice button, they are taken through a visualforce flow that lets them create the invoice directly in your accounting system when breadwinner successfully creates that invoice in the accounting system, it receives a confirmation message and uses it to replicate the invoice in salesforce so, by creating a validation rule, you aren't preventing anyone from creating an invoice in your accounting system you are only preventing breadwinner from copying that invoice back to salesforce—it would still be in the accounting system if you want to restrict invoice creation to specific situations, there are ways to do so you could have multiple page layouts and record types and, you could have all but one page layout without the "new invoice" button on the related list and, a workflow could change the record from the record type/page layout without the new invoice button to the record type/page layout with the new invoice button or, if you wish to restrict the creation of invoices to certain people, you could make the invoice object read only or not visible in their profile this would cause salesforce to automatically hide the new invoice button from them, even if it was in their page layout please be aware that the options listed above are standard salesforce functionality you can talk to your salesforce consultant about them if you wish for us to help you set up page layouts, you would need to be on our premier support plan, as our regular support plan covers breadwinner but does not cover consulting on standard salesforce functionality the article "account validation rules for breadwinner" expands on the use of validation rules on accounts when breadwinner is installed