DAP - parcelparty, plannedwork and general DAP information

Monday January 6th we will deploy the first DAP changes of 2025, and the changes is as follows:

Parcelparty table

• As announced on May 3rd we will remove data in some columns in the table f_parcelparty. And this is done to ensure compliance with GDPR regulations. We have had some delays in getting these changes into production, but on January 6th the following columns will no longer be populated, and any existing data in these columns will be removed.

  • Name

  • Email

  • Phone 1

  • Phone 2

• Impact on Your Operations: Please note that these modifications may necessitate adjustments on your end, particularly regarding automatic data extractions. We kindly request that you review your existing queries and procedures to accommodate these changes effectively. For those who have used the name column to identify sender shops we encourage you to switch to using the shop table which could be joined to a shipment with use of the f_shipmentbooking table.

Plannedwork table

• We have fixed an issue that occured when an existing employee got a new employment start date (ansatt dato).

  • An example could be in scenarios where an existing employee got a new position in the company or went from a temporary position to a permanent position resulting in a "new start date" for that position.

  • In the past this has affected the f_plannedwork table for entries related to the previous position and these entries was not present in the table.

  • The f_plannedwork would in these cases only show planned work after the "new start date".

  • With the improvement that will be deployed January 6th we will now also show historical data for the previous positions the employee had.

General information

During the last months we have made several improvements to the DAP documentation that could be found here.

We will continue improving the documentation, but please let us know if there is anything spesific you want us to focus on in the DB Docs.