Sophie_Lyons
Community TeamJoined 1 year ago
User Profile
Community Team
User Widgets
Contributions
7. How to Contribute to the Community (and Earn Rewards)
Contributing to the Community is a fantastic way to help others, expand your knowledge, and earn rewards. Here’s how you can make a difference and be recognized for your contributions: Answering Questions To find questions that need answers, check the quick links panel on the right-hand side. You'll see a link labeled "Someone Needs Help." Clicking on this will display a list of all questions without a 'Best Answer'. Types of Questions Unanswered Questions: These questions don’t have any answers or comments yet. They are at the top of the list and are a great starting point for providing assistance. Tentatively Answered Questions: These questions have comments or potential answers but are still awaiting a final resolution. Reviewing and contributing to these can also be valuable. Benefits of Helping You help out fellow Community members You can earn rewards (see below) Answering questions helps you learn more about the Quantexa Platform and its capabilities, enhancing your expertise. Earning Points and Badges Contribution Recognition By actively participating and helping out, you can earn points and badges. Here’s how: Commenting on Posts: Every comment you make contributes to your points tally. Best Answers: When your answers are marked as the best, you'll earn badges and additional points. Rewards and Leaderboards We have a dedicated Get Rewarded to highlight and promote achievements, Here, you can: View the full list of badges, their points value, and how to earn them. Check out the latest competitions. See the current month’s leaders on the leaderboard. Top contributors can win prizes and gain recognition as Members of the Month. Member of the Month Community Members of the Month not only receive a prize but also get a shout-out post on the Community. We'll also share the post with your Quatnexa Team and inform your managers to ensure your contributions are acknowledged within your team. Contributing to the Community is a win-win situation. You help others, improve your skills, and earn recognition and rewards! DemoDesigning for Efficiency: Lowering Quantexa TCO at Scale
APAC/ EMEA Friendly Time Tuesday, June 9th | 2:00 PM SGT | 4:00 PM AEST | 8:00 AM CEST Join our upcoming webinar with Senior Solution Architect, Iestyn Pryce, to uncover opportunities to reduce unnecessary spend, improve efficiency, and ensure you’re getting the best possible return from your Quantexa deployment. We’ll also explore how these gains are achieved in practice, from smarter data sharing and reuse to better utilisation of compute and platform resources across your environment. On the Agenda: Where your biggest cost drivers hide and what to do about them Quick wins you can implement this sprint What our customers changed to cut TCO Q&A Session Platform Directors, Enterprise and Solution Architects, Technical Leads, and BAs running Quantexa in production - we expect to see you! Please register below using your corporate email address: Learn more about optimising TCO in the Community Library: Quantexa TCO Optimization Guide: Key Cost Drivers and Actionable Recommendations Presenter Bio: Iestyn Pryce is a Senior Solution Architect at Quantexa with 15 years of experience delivering Decision Intelligence solutions. He leads Quantexa’s Delivery Best Practice initiative and supports customers with their Quantexa deployments across Banking, Insurance, and the Public Sector.Designing for Efficiency: Lowering Quantexa TCO at Scale
EMEA/NA Friendly Time Tuesday, June 9th | 3:00 PM BST | 4:00 PM CEST | 9:00 AM EST Join our upcoming webinar with Senior Solution Architect, Iestyn Pryce, to uncover opportunities to reduce unnecessary spend, improve efficiency, and ensure you’re getting the best possible return from your Quantexa deployment. We’ll also explore how these gains are achieved in practice, from smarter data sharing and reuse to better utilisation of compute and platform resources across your environment. On the Agenda: Where your biggest cost drivers hide and what to do about them Quick wins you can implement this sprint What our customers changed to cut TCO Q&A Session Platform Directors, Enterprise and Solution Architects, Technical Leads, and BAs running Quantexa in production - we expect to see you! Please register below using your corporate email address: Learn more about optimising TCO in the Community Library: Quantexa TCO Optimization Guide: Key Cost Drivers and Actionable Recommendations Presenter Bio: Iestyn Pryce is a Senior Solution Architect at Quantexa with 15 years of experience delivering Decision Intelligence solutions. He leads Quantexa’s Delivery Best Practice initiative and supports customers with their Quantexa deployments across Banking, Insurance, and the Public Sector.Guide For Business Analysts (BAs)
Ensure you're logged in to access all available content for BAs! Academy Quantexa Technical Business Analyst Academy (TBAA) The Quantexa Technical Business Analyst Academy is an in-depth program that gives learners the skills needed to become a Technical Business Analyst on a Quantexa project. Community Areas to Follow 🔔+ Product Releases Product Roadmap | Quantexa Community Blogs A day in the life of... a Technical Business Analyst It's Not About Data Quality Anymore. It's About Data Understanding. A BA Journey Through a Quantexa Implementation Process in the Capital Markets Industry Lessons Learned from Delivering Insurance Use Cases Community Library Data Ingestion Running a Data Discovery Process How to define and gather Data Requirements: A BA's Perspective Defining a detailed Document model design Understanding Data Cleansing and Parsing: A BA's Perspective Entity Resolution (ER) Entity Quality: The Good, The Bad, and The Ugly Recording Outcomes from Entity Resolution Review Entity Resolution General Playbook Exclusion Criteria Tips, Tricks, and Considerations ER: Tools Using Batch Resolver Tools for Entity Resolution Leveraging EQU: A Business Analyst's Perspective Leveraging EQO to Improve Entity Quality: A Business Analyst's Perspective Leveraging ORCA: A Business Analyst's Perspective Scoring & Alerting Scoring Concepts: Score Types and Score Output Levels Scoring Concepts: Scenarios & Risk Factors Scoring Concepts: Re-Alerting Individual Score Tuning Guidance Functional Scoring Validation Scoring Concepts: Network Generation & Design Delivery Validation Milestones for a Successful Quantexa Deployment Streaming Solutions Optimizing Entity Resolution and Graph Expansion to Enhance Performance of StreamingUnify: Step-by-step guide to using the workload
This page provides a step-by-step guide to setting up and using the Unify workload. The guide indicates where capabilities and features differ in the Demo version of the workload, which has restricted capabilities compared to the Full User and Trial versions. Overview The following steps provide a summary overview of your end-to-end process when using the Unify workload: Prepare your Data Sources. Launch the Quantexa Unify workload. Create a Project. Load your Data Sources. Loading your Data Sources automatically triggers Data Mapping of each Data Source. Review the output of the Data Mapping process and make any amendments if needed. Run an Iteration to conduct Entity Resolution. View your Iteration’s Entity Resolution results. The following diagram provides a visual overview of the workflow: Prerequisites Before proceeding to the Using the Unify workload section to start using the workload, complete the following prerequisites: Ensure your Fabric administrator has Enable Microsoft Fabric for your organization - Microsoft Fabric. Next, add the Unify workload to your Fabric tenant as follows: 2.1. From the Fabric home page, click the Workloads button in the left navigation pane. 2.2. From the Add more Workloads section shown below, click the Quantexa Unify workload. 2.3. You are taken to the Quantexa Unify workload introduction page. Click the green Add button in the summary header to add the workload. 2.4. Once added, the workload appears in the My Workloads section on the Workloads page. 2.5. For further details on adding workloads see the Microsoft tutorial. Next, someone in your organisation with the appropriate permissions, such as a Capacity, Tenant, or Workspace Administrator, must activate the Quantexa Unify workload. IMPORTANT: While the Unify workload can function in Fabric on a F1 or F2 capacity, Quantexa recommends using a F8 capacity at least. Before using the workload, you must also provide consent to the Quantexa application. Your organisation’s Workload Administrator will typically have provided consent on behalf of all users from your organisation already. However, if you experience any issues, contact your Workload Administrator. Finally, ensure you have prepared any Data Sources you want to use with the workload and that they are in a suitable format to upload as Lakehouse objects to Fabric. NOTE: For the Demo version of Unify, you cannot use your own Data Sources and must use those provided by Quantexa instead. Using the Unify workload The following steps guide you through using the Unify workload, after you have prepared your Data Sources and added the workload, and are separated into the following sub-sections: Creating your Project. Adding Data Sources. Data Mapping. Running an Iteration. Viewing and using the Unify output. (1) Creating your Project This section guides you through creating your Project in the Unify workload. After completing the prerequisites, navigate to the workspace you want to use the Unify workload in. IMPORTANT: The workspace you use the Unify workload in must have a Lakehouse to which the workload output can be sent. You can navigate to the workspace by clicking on the Workspaces item on the left-hand sidebar and selecting the workspace from the list. Clicking on your workspace in the list takes you to the workspaces homepage. Launch the workload by clicking + New item in the top left of your workspace’s homepage. This brings up a pop-up list of workloads on the right of the page. Click on the Unify workload you want to use from the Prepare data section. A pop-up titled New Project appears. IMPORTANT: If a permission request appears at this stage, click Agree. In the New Project pop up, type in a unique name for your Project that is easy for you to recall and identify. Click Create. You are then taken to the homepage of your Quantexa Unify Project. (2) Adding Data Sources Once on your Project homepage, see the Explorer panel on the left side of the page. This shows your Project’s Data Sources and Iterations. On setting up your Project for the first time, the panel will show that you do not have any Data Sources or Iterations. To add a Data Source, click Add Data Source using one of the following options: From the Explorer panel, click the + button next to Data Sources. From the menu under the Home tab, click Add Data Source. On the main section of the page, click Add Data Source. When you click Add Data Source, a pop-up appears listing the various Lakehouse objects you can choose as your Data Source. This is your OneLake catalogue. Select the Lakehouse you want to add as a Data Source and click Connect. NOTE: You can only add one Data Source at a time, so you must repeat this process for each Data Source you want to add. IMPORTANT: If you are using a Demo version of the Unify workload, you cannot upload your own Data Sources. Instead, you can only use the Data Sources Quantexa provides in Unify: Contoso and Northwind. (3) Automatic Data Mapping Once you have connected a Data Source, the Data Mapping process for that Data Source runs automatically. However, you have the capacity to make manual amendments too. Once the Data Mapping process completes, a Data Mapping table appears in the main section of the page. The table contains the following columns: Field: this is the column name pulled from the Data Source, such as Forename, CustomerAddress and Email. The key symbol against a field, for example against customerID , indicates that the field is a Primary Key. A Primary Key is a unique identifier for the Entity Resolution process. A field must be 100% unique and 100% populated to qualify as a Primary Key. Entity Mapping: this is the Entity Group that the Field is or that it maps to, such as Business, Individual or Email. Mapping Field: this is the Entity attribute that the Field maps onto, such as forename and dateOfBirthString . Type: this details the Field’s data type, such as Optional Int , String or Optional String . For example, the schema does not strictly require an Individual Entity Type to include a date of birth, making CustomerDoB an Optional String . Uniqueness: this measures how many distinct values there are as a percentage of total rows. Populated: this details the proportion of rows that have a value in this field. Distinct Values: this counts the distinct values within the field column. At the bottom of the Data Mapping section is an expandable Data Viewer panel. The panel shows the following: The Raw Data tab shows the field input strings that the Data Mapping process pulled from your Data Source. The Entity Data tab shows the cleansed, parsed and standardized output for that Data Source, mapped to Entity Resolution fields. Once the Data Mapping table appears, you are advised to review its outputs and amend the Data Mapping schema as needed. For example, the process may accidentally recognize three component parts of one address as a separate address each. In such cases, you may want to manually amend the mapping table. To manually amend the Data Mapping, complete the following steps: Review the main Data Mapping section and amend any of the Entity Mapping and Mapping Field allocations using the drop down options, as needed. Additionally, review the Manage Entities tab, under the Data Source tab. The relevant Data Source tab is the one next to the Home tab in the top left of the page: The Manage Entities tab allows you to review the Entity Types that are pre-populated by the Data Mapping process, and the Entity Groups within these Entity Types. Unify provides six different Entity Types. However, you can add new Entity Types as needed, and this feature is available in all versions of Unify except for the Demo version. Within the Manage Entities tab, the Entity Groups sub-tab lists out the Entity Groups for each Entity Type. Ensure you click through each Entity Type and review the Entity Groups, making any amendments as needed. For example, you may need to delete, add or edit Entity Groups as part of your Data Mapping review. IMPORTANT: Manage Entities does not currently allow you to edit the Matching Level at a granular level for each Entity Type. You may only specify the Matching Level at the Iteration run stage. IMPORTANT: Ensure that you review the Manage Entities tab for each of your Data Sources as there may be differences between the Data Sources. For example, in the Demo version, you will notice that the Entity Types for Contoso and Northwind are slightly different. You can resolve Entities within a single Data Source, such as where a database contains multiple entries per customer. However, Entity Resolution is typically used to resolve Entities across multiple Data Sources. Therefore, if you are using more than one Data Source, you must connect your second Data Source once the Data Mapping process for your first source completes. The Data Mapping process outlined in the preceding points repeats for the second Data Source and any subsequent Data Sources. (4) Running an Iteration Once your Data Sources are mapped, you can now resolve and create Entities by running an Iteration of the Unify Entity Resolution process. To run an Iteration, complete the following steps: Return to the Explorer panel on the left. Click the + next to Iterations. A New Iteration pop-up appears. Fill in the required details, with the following in mind: Provide a unique Iteration name that is easy to identify. Select the Data Sources you want to resolve in this specific Iteration. For example, if you have five different Data Sources, you may want to run multiple Iterations using different Data Source combinations each time. You may use any number of Data Sources in an Iteration, from a minimum of one. Choose the Matching Level for this Iteration. Select the Destination Lakehouse. This is the Lakehouse in which Unify outputs the Entity Resolution output tables. Click Run. The Iteration first completes some pre-processing jobs. It then resolves the Entities. The whole process can take approximately 10 minutes. Most of this time is spent on the overheads of setting up the jobs. Therefore, running 1 row, 1,000 rows or 100,000 million rows of data all take approximately the same time. The Quantexa system has been proven at 60 billion+ record volumes. NOTE: For the Demo version, the test files are intentionally small to allow you to easily view the results. Once complete, the page displays a summary of the Iteration as follows: The Information section on the top left contains administrative details about the Iteration. You can view further details by clicking on the Job Details button. The Total Entities section on the top right compares the number of input records against the number of resolved Entities in bar chart format, by Entity Type. The Output Data section at the bottom shows the Lakehouse tables created from the input records and the resolved Entities, by Entity type. This data is saved to the Lakehouse that you selected as your Destination Lakehouse in step 2. (5) Viewing the Unify output Once your Iteration is complete, you can view the Iteration output. These outputs are as follows: Entity Resolution Power BI Report Semantic Model of the Data Sources and the underpinning Entity Resolution tables For further detail on the content of these outputs, see Unify: Further guidance on selected key features. For further guidance on using the outputs in your workflow, see Unify: Example workflow. To view these outputs, complete the following steps: Return to the Workspace in which you set up your Unify workload. You can navigate to it using the Workspaces button on the left-hand navigation bar. A list of Fabric items, including your Workspace folder structure, is shown in the bottom panel of your Workspace. Scroll down through the list to find the following items, and click to open them: The Iteration’s Power BI Report. The Report has the same name as your Iteration, preceded by 'Quantexa: '. The Iteration’s Semantic Model, which includes the Entity Resolution tables. The Semantic Model has the same name as your Iteration. Once in the Semantic Model space, you can view the related Entity Resolution tables by clicking on each table in the right-hand Tables panel. To view the Semantic Model itself, click Open semantic model in the top menu bar. Support If you run into any issues while using the Unify workload, visit the Unify Support page. You can post a question outlining your issue and request for help or view previous posts to see if they answer your question. Next steps For an applied example of the step-by-step guide, including ways to use your Unify output downstream, see Unify: Example workflow.Data Engineer Academy (DEA) Core Platform Certification: Official Release & Program Overview
We are thrilled to announce the release of the Data Engineer Academy - Core Platform Certification. The Data Engineer Academy now offers two pathways: Core Entity Resolution (ER) Certification for learners working with the Entity Resolution component of the Quantexa Platform (already released). Core Platform Certification for learners seeking broader, end‑to‑end knowledge of the Quantexa Platform. What does the Core Platform Certification Cover? ETL: Data Ingestion and transformation Entity Resolution: Matching and linking data User Interface (UI) Configuration: Customising the Quantexa UI Scoring: Building and applying Scoring logic Key Enhancements & Benefits Alignment with Latest Platform Capabilities: All content is aligned with the latest Quantexa v2.8.x capabilities, ensuring that learners work with current tools and best practices. Optimized Time to Completion: The Core Platform program is estimated to take around 4.5 weeks full-time to complete. We estimate this is up to a 50% reduction compared to release 1. Modular Learning Journey: The program is structured into focused, manageable modules, typically ranging from 30–40 minutes each. Hands-on Practice: Learners will engage in practical activities and assessment tasks, guided by clear checklists. Each module includes hands-on practice, encouraging learners to work with their VDI and code simultaneously. Improved Learning Design: Multiple improvements have been implemented to enhance the overall learning experience, making it more usable, enjoyable, and focused on practical skills and tangible outcomes. Integrated Assessments: The program incorporates multiple knowledge checks and main assessments, including code reviews and live assessments, designed to provide frequent feedback and measure practical skills effectively. We are excited about the capabilities this new Certification will unlock for Engineers and look forward to your valuable feedback as you engage with the DEA Core Platform Certification! Key Information: Select the tabs to find out more.Sign Up for a Community Tour or Member Interview Today!
To ensure you’re getting maximum value from our Community we offer tours and member interviews. These initiatives offer you and your colleagues an opportunity to learn more about Community features, provide feedback, and connect with members of our Community team. 🚶♀️ Community Tour: A 30-minute demo of the Community, where we'll explore key features that will enhance your Quantexa journey. 🗣️ Member Interview: Engage in a 45-minute interview, focusing on your experience with the Community so far and any suggestions you may have for improvements. To sign up for a member interview or Community tour, please book a time in our diaries.QuanCon '26: Decoding Data + Decisions
3 March 2026 | The Brewery, London | Virtual worldwide Register Now! We’re thrilled to announce that our premier in-person and virtual event is back! QuanCon26 will take place at The Brewery in London on Tuesday, March 3, 2026, and virtually across the globe. What is QuanCon? QuanCon is Quantexa’s flagship annual customer and partner ecosystem event. It’s where executive-level leaders come together for a day of insightful presentations, valuable networking opportunities, and educational sessions designed to shape the next decade of data, AI, and enterprise transformation. This year’s theme, Decoding Data + Decisions, reflects the growing need for organizations to strengthen enterprise-wide insights and prepare for AI-driven disruption. QuanCon26 will give you an early look at the strategies, tools, and innovations global leaders are using to accelerate performance and deliver measurable outcomes. What’s New This Year? Hands-on Innovation Forums: Engage with our partners and Quantexa’s technology and industry experts in dedicated tracks featuring real-world case studies, reference architectures, live demos, and peer stories that showcase the power of Decision Intelligence across industries: Banking Track – The compliance dividend: Turning regulation into a catalyst for growth Insurance Track – Driving competitive advantage in insurance through an AI-ready future Government Track – From trusted data to trusted outcomes: Modernizing decision-making in government Data & AI Track – Building a contextual fabric to operationalize data products, trusted AI, and analytics Seats for Innovation Forums are limited. Learn more about each track and register now! Networking & Experience Zone: Connect with senior leaders, explore interactive demos, participate in engaging activation activities, and celebrate our milestone year.Unify: Further guidance on selected key features
This page provides further guidance on some key features of the Unify workload. Overview The selected features discussed on this page are those you will encounter as you use the Unify workload. This page provides further advice and guidance on using these features, in addition to their basic definitions on the Core Concepts page. Features The following sub-sections provide further detail on some of Unify's key features. Data Mapping For a definition of Data Mapping, see Unify: Core concepts. Data Mapping is an integral part of Quantexa’s Entity Resolution solution. Quantexa’s Data Mapping process in the Unify workload focuses on mapping your Data Sources to pre-defined Entity Type and Entity Group fields. In the context of the Unify workload, Data Mapping seeks to answer some initial questions about your Data Source such as the following: What source fields match the Unify Entity attribute fields? Which should they be mapped to? For source fields that do not directly match Unify’s pre-defined Data Mapping fields, what are the most suitable matches? If there are no suitable matches, why? What Entity Types and Entity Groups are being populated by the source data? To what percentage are these fields being populated? As noted in the step-by-step walkthrough, while you may edit the Data Mapping process output, the process itself runs automatically on loading a Data Source. This saves significant time and manual effort. However, to ensure accurate Data Mapping in Unify, your data must be in a suitable format and have some logical structure for the mapping process to read it effectively. Iterations For a definition of Iteration, see Unify: Core concepts. Running an Iteration serves two purposes: Conducting Entity Resolution on the Data Sources you include for that Iteration. Comparing Entity Resolution outputs across multiple Iterations that use different Data Sources, or different combinations of Data Sources. In addition to comparisons on the data content, an Iteration can help you compare data quality, Entity Resolution metrics and field population rates between your Data Sources. The first scenario is straightforward, and thanks to Quantexa’s Entity Resolution features within the Unify workload, you can use the workload to build a trusted data foundation directly. The second scenario would be more complex without the Unify workload, as it would require a significant investment of time and resources to conduct a true comparison. However, with the Unify workload, the complex is made simple. You simply run multiple iterations using the straightforward step-by-step process. Matching Levels For a definition of Matching Level, see Unify: Core concepts. The availability of Matching Levels helps you tailor Unify’s Data Mapping and Entity Resolution processes to your Project’s needs. As a reminder, there are three available Matching Levels within the Quantexa Unify workload: Default, Fuzzy, and Strict. The following are example use cases for Fuzzy and Strict Matching Levels. Fuzzy: You can use a Fuzzy Matching Level in a scenario like matching customers to a watchlist in the Financial Crime arena. Due to the seriousness of the matter, you want to ensure you find all possible matches. Even where there is Overlinking, you are happy to manually review the matches to find the correct ones. Strict: You can use a Strict Matching Level in a scenario like generating a master set of customers in Master Data Management. As the output may be used to trigger automatic action, such as contacting customers, and you are unlikely to review the matches, you want to ensure that all generated matches are correct. Even where there is Underlinking, you are happy to have a smaller scope of matches given the reputational and practical consequences of any incorrect matches. The following factors can help you decide which Matching Level to choose at the Data Mapping stage and for each Iteration: The quality of your Data Source. The completeness of your Data Source. Your particular use case. For example, if you are planning to use the Entity Resolution output to execute automated tasks without reviewing all matches, it may be better to use a Strict matching level. For cases where you want to ensure you have all possible matches, even with overlinking, you may want to use a Fuzzy matching level. If you are not sure which Matching Level to use, you can opt for the Default Matching Level, as this strikes a balance between Overlinking and Underlinking. Automated output After completing an Iteration, the Unify workload automatically outputs the results of the Entity Resolution process into the following: Iteration summary The summary shown for an Iteration after Entity Resolution is a bar-chart in the top-right corner. The bar chart shows a comparison between the total number of input Records against the total number of resolved Entities for each Entity Type. Power BI Report The automatic report shows summaries of key information for Entity Types, such as Entity size, Entities by Address and Entities by Business and Individual counts. Entity Resolution records tables and Entities tables Records tables show the records that triggered the resolution of a particular Entity. For example, the workload outputs multiple tables showing the relevant records for a particular Entity. Each record table covers a specific Entity type, such as Individual or Address. Entities tables show the Entities the source data has resolved to. For example, you may input two Data Source tables, and after Entity Resolution, the workload outputs multiple additional tables showing the resolved Entities. Each table covers a specific Entity type, such as Individual or Address. Semantic Model An Iteration’s Semantic Model shows the relationships between the tables described in the preceding point and your input Data Source tables, within an Iteration. For further information on Semantic Models in Microsoft Fabric, see Power BI Semantic Models in Microsoft Fabric. Additionally, using the automatic outputs, you can optionally create other outputs within the broader Fabric suite, including the following: Other types of Power BI reports Power BI is a functionality provided by Microsoft Fabric, and not by the Unify workload. Power BI reports are typically based on one Semantic Model and can feature visualizations such as charts, graphs and tables to provide data insights. They can help you explore your data – and the output of Unify – further. For more information on Power BI reports, see Reports in Power BI. Notebooks Power Query (M script) with Dataflow Gen2 Next steps For a guide to using the Unify workload, see Unify: Step-by-step guide to using the workload. For an applied example of the step-by-step guide, see Unify: Example workflow.
My User Groups
Business Analysts (BAs)
Financial Crime Global
This public group welcomes customers, partners, colleagues, and thought leaders to share expertise, insights, and innovative practices in leveraging the Quantexa Platform to fight financial crime and fraud worldwide.Financial Crime Leaders Group (Europe)
Would you like to join a Group?
