HOMEBUILDER: SALEFISH - LIMITATIONS AND TECHNICAL NOTES

Back to the SaleFish - HomeBuilder Title Page

Limitations, Notes of Caution and Specific Data Creation Rules (Please Read)

• This is a one-way integration, only transactions from SaleFish are updated in HomeBuilder, any changes to HomeBuilder are not updated in SaleFish.
• There are differences in the requirements and standard setups of SaleFish and HomeBuilder.
  • Phase is mandatory in HomeBuilder and although not mandatory in SaleFish, the integration will not work without creating a Phase and assigning it to all Lots.
  • If you are sharing an integration with another builder in SaleFish, you must have Phases that are not the same as your partner builder.
  • Lot numbering should have the same number of digits for all Lots otherwise the sorting works poorly in HomeBuilder. For instance, numbering like 009, 010, 016 works well; numbering like 9, 10, 16 does not.
  • One Model in SaleFish will create multiple models in HomeBuilder if there are elevations. One Model per Elevation.
    • An example of this is where in SaleFish the Model is PAX-335 and there are three Elevations: A, B or C. Three Models will be created in HomeBuilder as follows:
      • PAX-335-A
      • PAX-335-B
      • PAX-335-C
    • Notes:
      • The description in SaleFish is the one used for each of the Models in HomeBuilder. The Elevation is not part of the description, you need to refer to the Model code or elevation to know the elevation.
      • If you forget to put the elevation on the Lot in SaleFish, the synchronization will fail.
    • Information will be overwritten without warning:
      • It is expected that Lot Installments are created in SaleFish and transferred to HomeBuilder. It means that you should not use HomeBuilder to record Installments. Be aware of these situations:
        • If you change a Lot Installment in HomeBuilder, it will be overwritten by the SaleFish value without warning the next time the integration runs.
        • The Lot Installment in HomeBuilder is just a “worksheet” entry used to supply the journal to post. This journal value can be adjusted prior to posting or the Lot Installment entry can be changed at any time even after posting the installment. To track changes the value before posting is retained on the line for reference.
        • If the Lot purchaser is changed in SaleFish, this does not automatically delete or change the Installments on the Lot, this must be done in SaleFish after the purchaser has changed.
      • You may need to create new records in HomeBuilder to accommodate the types of records that SaleFish uses. An example of this is a “reserved” home. This type of thing is covered in setup but be aware that unless you review the SaleFish log in HomeBuilder from time to time, you may have records that are not coming through; to aid with this, we have provided a “Log” cue in HomeBuilder. Make sure that someone has this cue on their main page and has the responsibility of checking it every day.

Technical Notes and Definitions

• SaleFish is a "simple streamlined and secure platform for real estate transactions and for builders to sell new homes."
• "HomeBuilder SaleFish Integration" is an application for Microsoft Dynamics 365 Business Central available from Microsoft’s AppSource. This App is installed on top of the HomeBuilder App. The App retrieves records of models, lots, Lot sales statuses, and purchasers.
• The technology used to pull information in from SaleFish is an API in JSON format and it is expected to be run on a periodic basis using Dynamics’ Job Queue system (setup details shown later in this document).