Skip to main content

Export

Description​

There are some IDs we need to caryover from BDX exactly as is (to use IDs for data export).

In “BDX Live” each combination of division + brand is a separate division. Our CMS stores only unique divisions (Like "Austin", but Division may have many brands).

To preserve data structure for BDX feeds and to avoid any issues with data sync, we need to keep these IDs exactly as is.

For Division:​

  • Division Number=(Builder Number)
  • Division Name=(Reporting Name)
  • Brand=(Brand Name)

For Community:​

  • Community Numbers=(Subdivision Number)
  • Community Names=(Subdivision Name)

Structure Example​

In our database, Austin is a single division which has 2 brands: "Brightland Homes" and "Gehan". Austin division has a list assigned communities.

But in BDX “Austin” must brake down into 3 divisions with unique IDs and its own communities in BDX Live because it has 3 brands.
Single division of “Austin” becomes:

  • Brightland Homes - Austin
  • Brightland Homes - Austin (GP)
  • Gehan Homes - Austin

Each with its own set of IDs, and communities.

So, during export, all IDs listed above, should also be saved, and all communities also go into separate division:
For example (numbers are just for example), if our "Austin" division has 20 communities, 10 communities may go into "Brightland Homes - Austin", 5 into "Brightland Homes - Austin (GP)" and 5 in to "Gehan Homes - Austin".

XML for Export​

Example: Feed file has "Bulders" parent element. Single Corporation element with 2 IDs (can be hardcoded as will never change):

  • Corporate Number=Corp Geh951
  • Corporate Name=Brightland Homes
  • Corporate State=TX

"Builder" element (which is the division, like "Austin")
Builder element has "Subdivision" element (which is community)

XML file for export will have this structure:

<Builders xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" DateGenerated="2023-08-09T16:00:35"
   FileID="1">
   <Corporation>
      <CorporateBuilderNumber>Corp Geh951</CorporateBuilderNumber>
      <CorporateState>TX</CorporateState>
      <CorporateName>Brightland Homes</CorporateName>

      <Builder>
         <BuilderNumber>Div Geh952</BuilderNumber>
         <BrandName>Brightland Homes</BrandName>
         <ReportingName>Brightland Homes - Austin</ReportingName>
         <Subdivision>
            Community data goes here
         </Subdivision>
      </Builder>


      <Builder>
         <BuilderNumber>GrayPointAustin</BuilderNumber>
         <BrandName>Brightland Homes</BrandName>
         <ReportingName>Brightland Homes - Austin (GP)</ReportingName>
         <Subdivision>
            Community data goes here
         </Subdivision>
      </Builder>


      <Builder>
         <BuilderNumber>Div GehAUS1</BuilderNumber>
         <BrandName>Brightland Homes</BrandName>
         <ReportingName>Gehan Homes - Austin (GP)</ReportingName>
         <Subdivision>
            Community data goes here
         </Subdivision>
      </Builder>


   </Corporation>
</Builders>

Feed Examples​

For reference:

XML Feed File Example: XML File


Official BDX XML Mapping documentation:

Download PDF