Continuity amongst data levels and relationship-based data can be challenging to achieve. Typically modifications or updates made at one level do not necessarily impact other levels of data. Due to the complexity of data structure, this often has to be achieved through tedious manual entry and re-entry.
Some typical examples between this type of data exchange often happens at workflow-based records “syncing” back to static records. Common examples include:
- A new opportunity is won in a pipeline, the account and contact “Status” change from “Prospect” to “Client.”
- A new opportunity is won, and a contract start date needs to be designated and generated at a contract level.
- Throughout the sales process, key details like a contact’s “Industry” designation are changed or discovered. The contact’s account also needs updating to keep the data clean (think marketing needs, etc.).
- New hire candidates are added to a workflow-based record and when someone is hired, their status as an employee needs to be created/modified along, and the position they’re filling changed to no longer available.
These examples are endless. One essential piece of information to remember is that all these can be multi-level and are not limited to only one singular update. Countless updates can be made based on any condition or interaction with the original record.
Watch the video below and consider how Kizen can keep your data up to date and in sync.