Skip to content

Mapping

Many changes and upgrades

  • Two new shared collection classes:
  • Changes to Department class:
    • Reduced to one name (Name).
    • Removed WebPublish.
    • Removed RentBroker.
    • Removed Order.
    • Removed ServiceAreaPostalCodes.
    • More.
  • Changes to Estate class:
    • ID without prefix.
    • Tag is enabled as field for old ID from WebMegler.
    • Removed ExternalLinks.
    • Documents and Images as collection list.
    • More.
  • General changes:
    • OriginData changed to CustomData.
    • Added LastModifiedLocal as supplement to LastModifiedOrigin.
    • All nullable types marked with ?.
    • More.

Info

All fields from Vitec API endpoints (Employee, Department, Estate, Images, and Documents) are represented in the C# models for convenience.

Fields that have not yet been decided upon, or are planned for exclusion, are commented out. This makes it easy to include them later when testing with real data, if needed.

The Vitec integration tables provide an overview of what is currently commented out. All entries marked as "TBD" in the "Maps To (Destinet)" column indicate that the field exists in the models but is commented out.

Significant changes

  • I have changed the four base models, created more sub classes and shared classes.
    • It should now be much easier to match up against Vitec, while at the same time be flexible enough to be system-independent.
  • Document.cs and Image.cs has been given a LastModified field.
  • SystemID has been replaced by Origin, and SystemMetadatato CustomData, to better indicate that it is ID and data from the external source.
  • All fields from the selected Vitecs Swagger endpoints are displayed as tables on Vitec integration.
    • All fields with "TBD" in the "Maps to (Destinet)" column is in the respective models, but commented out. That makes it easy for us to include it if needed.
  • Vitec enum mappings displays mappings for all current enum values used in the models.
  • All model pages on this site includes newest files for download. Both base models, sub classes and shared classes.

Table for Vitec endpoints

I have created a table that displays all basic Vitec endpoints.

I hope to map all values to our new model here, and write notes as I go along.

What I had not thought about was all the enums! How we are going to solve that in a system-independent model? Create a transformation layer? A transformation or mapping utility that runs before the data is deserialized into our universal model?

Please note that this is a work in progress.