Setting Up Your API Data Correctly for FitUp Import

Setting Up Your API Data Correctly for FitUp Import

Weather you are setting up your project in Attainia or 4Tower, you will need to ensure the data is set up correctly in that 3rd party system to carry over to FitUp correctly. Below are some helpful tips on how to set up that data properly in those systems.

Location Information

Building Name

It is best to create a name for your building. When doing so, ensure that when you create your project in FitUp, the name of the building matches what you have in either 4Tower or Attainia. If this building doesn't match, the system will not be able to pull in the data correctly into FitUp.

Rooms

When setting up rooms, for items, it is best to use the Architectural Room Number for the Room Number field. This is how locations are identified in FitUp and linked to products. Using the room name in the room number field will not carry over to FitUp, causing the items to be uploaded without locations.

If you have multiple room numbers within the Room Number field in Attainia/4Tower, please ensure they are separated by a comma. This will allow our system to be able to upload the items per room in the list.

Know Your Settings in FitUp for Your Connection Type

We have several settings to manage your data as it comes into FitUp. Below are the settings and what they mean to you when you are setting up your data.

Quantity Settings

This setting sets the product quantity (or qty) to break out in FitUp. Some projects have large quantities of products that do not need to be tracked individually. The number entered in this field lets FitUp know to break out anything less than the number entered in the field.
The default number is 100. In this case, FitUp will break up products into individual line items for products with a quantity of 99 or fewer.


Sync Status Settings

This is the status Cutoff at which the products will no longer sync data from Attainia/4Tower to FitUp. The product status order is the order in which a product will
progress through the project.
The default is set to Purchased, which means that if a product is in status of Purchased or beyond in Attainia/4Tower, Attainia/4Tower will no longer update data for this product in FitUp. The dropdown menu shows all product statuses, listed in chronological order. In this case, FitUp would not receive data from Attainia about products that are in the Purchased, Vendor Confirmed Delivery, Staged, Received at Warehouse, Requested from Warehouse or other later statuses.


Mapped Fields 

When you are importing products into FitUp, we offer different fields to be mapped to our data. Below are the settings and what they mean to you when you are setting up your data.

Condition Mapping

4Tower offers two different fields to map the condition of products: Funding Source or Item State. Review the below snapshots to think about how you will be mapping the Condition of your product from Attainia/4Tower to FitUp.


Attainia uses the Funding Source to map the condition of products.


Status Mapping

Both 4Tower & Attainia use the ItemStatus field to map to FitUp Status. Review the below snapshot to think about how you will be mapping the Status of your product from Attainia/4Tower to FitUp.


Field Mapping

There are several fields that are currently mapped from Attainia/4Tower to FitUp. Below are the current fields that are mapped from each 3rd party application. Review these to think about how your data is set up and how it will be mapped to FitUp.

Attainia Fields



4Tower Fields