Skip to main content

Import

Description​

Data import is required to import data from "BDX Live" during the project launch.

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

In current platform “BDX Live” each combination of division + brand is a separate division. We switched to a simplified version in our CMS (Division may have many brands). But we need to keep some data, to create multiple divisions for export.

To preserve data structure for data exports and to avoid any issues with data sync with BDX, 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 new 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” is broken 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 import, all IDs listed above, should also be saved, but all communities merged into single "Austin" division.

Feed Examples​

For reference:

XML Feed File Example: XML File


Official BDX XML Mapping documentation:

Download PDF

Data Feed Location:​

Combined feed which contains all data from BDX. Updated on daily basis.

Bucket = feeds.brighlandhomes.com
Key = data/json/Unmodified_CombinedFeed.json
s3://feeds.brightlandhomes.com/data/json/Unmodified_CombinedFeed.json

URL: https://s3.us-east-2.amazonaws.com/feeds.brightlandhomes.com/data/json/Unmodified_CombinedFeed.json