Locations

Workflows > Endpoints > Dimension Entities > Locations

Purpose: Retrieve or update location details.

This workflow is typically used in cases where the location dimension is of relevance for transactions posted to or retreived from Go. It is also needed in cases where the integrating party need to synchronize location information to make sure that PowerOffice Go and their own systems have the same information about their locations. Location can also be set on projects in Go.

Regardless of the direction of the data flow, we highly recommend that the integrating party store the Id's of the PowerOffice objects. In general, the id's of all the various PowerOffice entities are the preferred mapping key, as they are uniquely assigned by the system and cannot be changed.

Endpoint

Description of core flow


Synchronize to Go:

  1. Check whether the location object already exists in Go

  2. Create or update information

Synchronize from Go

  1. Check if there are any new or newly updated locations in Go

  2. Retrieve the desired fields and information

Prerequisites

  • Access to the location access privelige

  • The client need at least one active subscription of a PowerOffice Go module

Related workflows:

General relevance for most api workflows if location is used as a dimension

Dictionary/Terminology

Location is one of the available dimensions that can be used on transactions i Go, for reporting purposes (ie grouping transactions on given locations when reporting). Location is typically interpreted and used as physical locations (warehouse, area of location for projects etc), but the dimension can be used for the information the client see fit.