Data modeling depends on trust. If the model does not preserve the right relationships, transformations, mappings and profiling context, teams lose confidence in what they are building.
WhereScape 3D 9.0.6.3 focuses on that trust layer: improving data integrity, strengthening validation, increasing reliability and making key modeling workflows faster & more predictable.
We are calling this the ‘Data Integrity’ Release.
It is a release designed to help teams move through discovery, profiling, modeling and conversion workflows with fewer interruptions, fewer configuration surprises and stronger confidence that the model accurately represents the data environment they are working with.
Faster Core Modeling Workflows
What’s changed: 3D now delivers improved performance across several core modeling workflows, especially when working with entity properties.
Users should see faster response times when:
- Deleting columns in the entity properties screen.
- Reordering columns in the entity properties screen.
- Merging large or complex models.
Why it matters: data modeling work often involves iteration. Teams typically discover, profile, review, adjust, split, merge and refine models; as they move closer to a trusted design. Small delays in high-frequency workflows can add up quickly, especially in larger environments.
Practical impacts include:
- Spend less time waiting while making routine model changes.
- Work more comfortably with larger and more complex models.
- Move faster through iterative design and review cycles.
Export Sample Data With More Flexibility
What’s changed: the Export Sample Data workflow now supports custom query templates and source sets.
Why it matters: not every team relies on default template configurations. For users working with more customized environments, sample exports need to respect the same flexibility as the broader workflow.
In previous scenarios, users relying on non-default template configurations could hit errors when exporting sample data. This update now removes that blocker.
Practical impacts include:
- Use custom query templates during sample export workflows.
- Support source sets that reflect your real environment.
- Make profiling, testing and review workflows easier to adapt.
Extensible Connections & Discovery Enhancements
What’s changed: 3D now includes fixes to the extensible connection framework, making discovery behavior more predictable and efficient.
A key improvement ensures that browse scripts are only executed once per discovery across relevant workflows.
Why it matters: extensible connections are important for teams that need to reach beyond standard discovery patterns. Predictable script execution reduces unnecessary overhead and helps keep discovery behavior easier to understand, troubleshoot and repeat.
This release also adds the WSL_WRKFL_Category environment variable for profiling scripts, giving teams more flexibility when scripting profiling logic.
Practical impacts include:
- Avoid unnecessary repeated browse script execution.
- Gain more predictable extensible connection behavior.
- Add more context-aware logic to profiling scripts.
- Improve discovery efficiency across customized workflows.
Stronger Configuration and Validation
What’s changed: 3D now includes improved validation and error handling around duplicate workflow set names and duplicate data type mapping names.
The release also fixes handling for multiline extended property values in delete extended property Model Conversion Rules.
Why it matters: configuration issues can be frustrating because they often surface later in the process, after teams have already invested time in setup, modeling or conversion workflows.
By catching more issues earlier and handling edge cases more gracefully, 3D helps reduce avoidable rework.
Practical impacts include:
- Prevent duplicate workflow set names from creating downstream problems.
- Prevent duplicate data type mapping names from causing configuration issues.
- Handle multiline extended property values more accurately.
- Strengthen confidence in repeatable configuration management.
Data Integrity Where It Matters Most
What’s changed: several fixes in this release are directly focused on preserving and representing data correctly throughout modeling workflows.
The transformation column is now retained when applying the Split Entities per Source Mapping Set conversion rule with no source set defined and Remove Parent Entity enabled.
Profiling scripts now receive the correct model version data, rather than stale output from the most recent connection-level discovery.
Why it matters: these are the kinds of details that protect the integrity of the model. If transformation metadata is lost during a conversion workflow, or profiling scripts receive the wrong discovery context, downstream design decisions can be affected.
This release helps ensure that what users see, profile and convert is a more accurate reflection of the model version they intend to work with.
Practical impacts include:
- Retain transformation columns during relevant entity splitting workflows.
- Ensure profiling scripts receive the expected model version context.
- Reduce the risk of stale discovery output influencing profiling.
- Preserve more accurate metadata throughout the design process.
Greater Reliability and Stability
What’s changed: 3D now handles several edge cases more gracefully, including scenarios where invalid profiling script output could previously cause the application to freeze.
Instead of locking up, 3D now displays appropriate error messages when invalid JSON output is returned from a profiling script.
The release also resolves a past issue where duplicate relationships could be discovered during the discovery process, which could create problems in later workflow steps.
Why it matters: modeling tools need to be resilient. When something goes wrong, we know that our users need a clear error message rather than accidentally creating a hidden modeling issue that will likely become harder to diagnose later.
Practical impacts include:
- Receive proper error messages when a profiling script output is invalid.
- Avoid application freezes in affected profiling scenarios.
- Prevent duplicate relationships from being introduced during discovery.
- Reduce interruptions during discovery, profiling and conversion workflows.
Typical Scenario: From Discovery to Trusted Model
A typical workflow might look something like this:
- Discover source systems through standard or extensible connections.
- Profile the model using scripts that now receive the correct model version context.
- Apply model conversion rules while preserving important transformation metadata.
- Merge larger or more complex models with improved performance.
- Validate configuration earlier to avoid duplicate workflow or mapping issues.
- Export sample data with custom query templates and source sets when needed.
Results of the latest release: it provides a smoother path from source discovery to trusted model design, with fewer manual interruptions and stronger confidence in the metadata that drives downstream automation.
Overall: Why This Release Matters
Our ‘Data Integrity’ Release is not just about fixing edge cases. It is about protecting the confidence users need when they rely on 3D as the visual design and modeling layer for automated data infrastructure.
Key benefits include:
- Better modeling performance: faster entity edits and improved model merging.
- More accurate metadata preservation: transformation columns and profiling context are handled more reliably.
- Stronger workflow flexibility: Export Sample Data now supports custom query templates and source sets.
- More resilient configuration: duplicate workflow set names and data type mapping names are validated more effectively.
- Improved discovery behavior: extensible connections now behave more predictably.
- More stable: invalid profiling script output now returns clear errors, instead of freezing the application.
Recap: Release Highlights
- Enhanced performance when deleting or reordering columns in entity properties.
- Enhanced performance when merging models.
- Export Sample Data now supports custom query templates and source sets.
- Browse scripts now execute only once per discovery in relevant extensible connection workflows.
- WSL_WRKFL_Category is now available for profiling scripts.
- Duplicate workflow set names and data type mapping names now have improved validation.
- Multiline extended property values are now handled correctly by delete extended property MCRs.
- Transformation columns are now retained during relevant entity splitting workflows.
- Profiling scripts now receive the correct model version data.
- Invalid profiling script output now returns an error message instead of freezing 3D.
- Duplicate relationships are no longer introduced during the affected discovery process.
Ready to try WhereScape 3D 9.0.6.3 ‘Data Integrity’ features in your environment? Reach out to us for a demo.
