purview
216 TopicsPurview Data Quality Dashboard/ Report - Refresh
Hi All, Currently I am getting all blank in Purview Data quality dashboard, before two months dashboard shows all values across each data quality dimensions and showed graph for each quadrant in a dashboard. After two months when checked the dashboard everything is blank nothing is shown in the report. (Note : I have created two governance domain and each domain has five data products assigned with data assets, implemented data quality rules on top of each data assets that time scores were reflected in the Purview data quality dashboard), but suddenly now it all went blank scores showing as 'blank' Note : None of the data quality assessment were not deleted during that two months, data quality rules are still active and its still showing scores at data asset level. But its not showing in the dashboard currently. Can you please help me to sort out, is there any refresh policy associated for Purview Data quality dashboard.82Views0likes7CommentsDefault Label and Justification Suddenly Stopped Working
Hi, Sometime last week, default labels for documents suddenly stopped working, it still works for emails. Also, there is a configuration where users have to provide a justification to lower a sensitivity label, that stopped working as well. This has all been in place since May and have always worked but just suddenly stopped working last week. I created a new label with the exact configuration to test, but that works perfectly. I have tried recreating the labels that do not work anymore, but nothing changed. Has anyone experienced this and how did you go about it. Thanks, Aishat15Views0likes1CommenteDiscovery for email attachment with encrypted sensitivity labels
We are currently testing encrypted sensitivity labels in conjunction with eDiscovery. We applied an encrypted label to a document, and eDiscovery was able to successfully search for the content in both OneDrive and SharePoint. However, the same functionality does not appear to work for email attachments—the content of encrypted attachments is not searchable. Are there any specific settings or configurations that need to be enabled to support encrypted email attachments in eDiscovery? Thanks3Views0likes0CommentsSafeguard & Protect Your Custom Copilot Agents (Cyber Dial Agent)
Overview and Challenge Security Operations Centers (SOCs) and InfoOps teams are constantly challenged to reduce Mean Time to Detect (MTTD) and Mean Time to Respond (MTTR). Analysts often spend valuable time navigating multiple blades in Microsoft Defender, Purview, and Defender for Cloud portals to investigate entities like IP addresses, devices, incidents, and AI risk criteria. Sometimes, investigations require pivoting to other vendors’ portals, adding complexity and slowing response. Cyber Dial Agent is a lightweight agent and browser add-on designed to streamline investigations, minimize context switching, and accelerate SecOps and InfoOps workflows. What is Cyber Dial Agent? The Cyber Dial Agent is a “hotline accelerator” that provides a unified, menu-driven experience for analysts. Instead of manually searching through multiple portals, analysts simply select an option from a numeric menu (1–10), provide the required value, and receive a clickable deep link that opens the exact page in the relevant Microsoft security portal. Agent base experience The solution introduces a single interaction model: analysts select an option from a numeric menu (1–10), provide the required value, and receive a clickable deep link that opens the exact page in the Microsoft Defender, Microsoft Purview, Microsoft Defender for Cloud portal. Browser based add-on experience The add-on introduces a unified interaction model: analysts select an option from a numeric menu (1–10), enter the required value, and are immediately redirected to the corresponding entity page with full details provided. Why It Matters Faster Investigations: Analysts pivot directly to the relevant entity page, reducing navigation time by up to 60%. Consistent Workflows: Standardized entry points minimize errors and improve collaboration across tiers. No Integration Overhead: The solution uses existing Defender and Purview URLs, avoiding complex API dependencies. Less complex for the user who is not familiar with Microsoft Defender/Purview Portal. Measuring Impact Track improvements in: Navigation Time per Pivot MTTD and MTTR Analyst Satisfaction Scores Deployment and Setup Process: Here’s a step-by-step guide for importing the agent that was built via Microsoft Copilot Studio solution into another tenant and publishing it afterward: Attached a direct download sample link, click here ✅ Part 1: Importing the Agent Solution into Another Tenant Important Notes: Knowledge base files and authentication settings do not transfer automatically. You’ll need to reconfigure them manually. Actions and connectors may need to be re-authenticated in the new environment. ✅ Part 2: Publishing the Imported Agent Here’s a step-by-step guide to add your browser add-on solution in Microsoft Edge (or any modern browser): ✅ Step 1: Prepare and edit your add-on script Copy the entire JavaScript snippet you provided, starting with: javascript:(function(){ const choice = prompt( "Select an option to check the value in your Tenant:\n" + "1. IP Check\n" + "2. Machine ID Check\n" + "3. Incident ID Check\n" + "4. Domain-Base Alert (e.g. mail.google.com)\n" + "5. User (Identity Check)\n" + "6. Device Name Check\n" + "7. CVE Number Check\n" + "8. Threat Actor Name Check\n" + "9. DSPM for AI Sensitivity Info Type Search\n" + "10. Data and AI Security\n\n" + "Enter 1-10:" ); let url = ''; if (choice === '1') { const IP = prompt("Please enter the IP to investigate in Tenant:"); url = 'https://security.microsoft.com/ip/' + encodeURIComponent(IP) + '/'; } else if (choice === '2') { const Machine = prompt("Please enter the Device ID to investigate in Tenant:"); url = 'https://security.microsoft.com/machines/v2/' + encodeURIComponent(Machine) + '/'; } else if (choice === '3') { const IncidentID = prompt("Please enter the Incident ID to investigate in Tenant:"); url = 'https://security.microsoft.com/incident2/' + encodeURIComponent(IncidentID) + '/'; } else if (choice === '4') { const DomainSearch = prompt("Please enter the Domain to investigate in Tenant:"); url = 'https://security.microsoft.com/url?url=%27 + encodeURIComponent(DomainSearch); } else if (choice === %275%27) { const userValue = prompt("Please enter the value (AAD ID or Cloud ID) to investigate in Tenant:"); url = %27https://security.microsoft.com/user?aad=%27 + encodeURIComponent(userValue); } else if (choice === %276%27) { const deviceName = prompt("Please enter the Device Name to investigate in Tenant:"); url = %27https://security.microsoft.com/search/device?q=%27 + encodeURIComponent(deviceName); } else if (choice === %277%27) { const cveNumber = prompt("Enter the CVE ID | Example: CVE-2024-12345"); url = %27https://security.microsoft.com/intel-profiles/%27 + encodeURIComponent(cveNumber); } else if (choice === %278%27) { const threatActor = prompt("Please enter the Threat Actor Name to investigate in Tenant:"); url = %27https://security.microsoft.com/intel-explorer/search/data/summary?&query=%27 + encodeURIComponent(threatActor); } else if (choice === %279%27) { url = %27https://purview.microsoft.com/purviewforai/data%27; } else if (choice === %2710%27) { url = %27https://portal.azure.com/#view/Microsoft_Azure_Security/SecurityMenuBlade/~/AscInformationProtection'; } else { alert("Invalid selection. Please refresh and try again."); return; } if (!url) { alert("No URL generated."); return; } try { window.location.assign(url); } catch (e) { window.open(url, '_blank'); } })(); Make sure it’s all in one line (bookmarklets cannot have line breaks). If your code has line breaks, you can paste it into a text editor and remove them. ✅ Step 2: Open Edge Favorites Open Microsoft Edge. Click the Favorites icon (star with three lines) or press Ctrl + Shift + O. Click Add favorite (or right-click the favorites bar and choose Add page). ✅ Step 3: Add the Bookmark Name: Microsoft Cyber Dial URL: Paste the JavaScript code you copied (starting with javascript:). Click Save. ✅ Step 4: Enable the Favorites Bar (Optional) If you want quick access: Go to Settings → Appearance → Show favorites bar → Always (or Only on new tabs). ✅ Step 5: Test the Bookmarklet Navigate to any page (e.g., security.microsoft.com). Click Microsoft Cyber Dial from your favorites bar. A prompt menu should appear with options 1–10. Enter a number and follow the prompts. ⚠ Important Notes Some browsers block javascript: in bookmarks by default for security reasons. If it doesn’t work: Ensure JavaScript is enabled in your browser. Try running it from the favorites bar, not the address bar If you see encoding issues (like %27), replace them with proper quotes (' or "). Safeguard, monitor, protect, secure your agent: Using Microsoft Purview (DSPM for AI) https://purview.microsoft.com/purviewforai/ Step-by-Step: Using Purview DSPM for AI to Secure (Cyber Dial Custom Agent) Copilot Studio Agents: Prerequisites Ensure users have Microsoft 365 E5 Compliance and Copilot licenses. Enable Microsoft Purview Audit to capture Copilot interactions. Onboard devices to Microsoft Purview Endpoint DLP (via Intune, Group Policy, or Defender onboarding). Deploy the Microsoft Purview Compliance Extension for Edge/Chrome to monitor web-based AI interactions. Access DSPM for AI in Purview Portal Go to the https://compliance.microsoft.com. Navigate to Solutions > DSPM for AI. Discover AI Activity Use the DSPM for AI Hub to view analytics and insights into Copilot Studio agent activity. See which agents are accessing sensitive data, what prompts are being used, and which files are involved. Apply Data Classification and Sensitivity Labels Ensure all data sources used by your Copilot Studio agent are classified and labeled. Purview automatically surfaces the highest sensitivity label applied to sources used in agent responses. Set Up Data Loss Prevention (DLP) Policies Create DLP policies targeting Copilot Studio agents: Block agents from accessing or processing documents with specific sensitivity labels or information types. Prevent agents from using confidential data in AI responses. Configure Endpoint DLP rules to prevent copying or uploading sensitive data to third-party AI sites. Monitor and Audit AI Interactions All prompts and responses are captured in the unified audit log. Use Purview Audit solutions to search and manage records of activities performed by users and admins. Investigate risky interactions, oversharing, or unethical behavior in AI apps using built-in reports and analytics. Enforce Insider Risk and Communication Compliance Enable Insider Risk Management to detect and respond to risky user behavior. Use Communication Compliance policies to monitor for unethical or non-compliant interactions in Copilot Studio agents. Run Data Risk Assessments DSPM for AI automatically runs weekly risk assessments for top SharePoint sites. Supplement with custom assessments to identify, remediate, and monitor potential oversharing of data by Copilot Studio agents. Respond to Recommendations DSPM for AI provides actionable recommendations to mitigate data risks. Activate one-click policies to address detected issues, such as blocking risky AI usage or unethical behavior. Value Delivered Reduced Data Exposure: Prevents Copilot Studio agents from inadvertently leaking sensitive information. Continuous Compliance: Maintains regulatory alignment with frameworks like NIST AI RMF. Operational Efficiency: Centralizes governance, reducing manual overhead for security teams. Audit-Ready: Ensures all AI interactions are logged and searchable for investigations. Adaptive Protection: Responds dynamically to new risks as AI usage evolves. Example: Creating a DLP Policy in Microsoft Purview for Copilot Studio Agents In Purview, go to Solutions > Data Loss Prevention. Select Create Policy. Choose conditions (e.g., content contains sensitive info, activity is “Text sent to or shared with cloud AI app”). Apply to Copilot Studio agents as the data source. Enable content capture and set the policy mode to “Turn on.” Review and create the policy. Test by interacting with your Copilot Studio agent and reviewing activity in DSPM for AI’s Activity Explorer. ✅ Conclusion The Cyber Dial Agent combined with Microsoft Purview DSPM for AI creates a powerful synergy for modern security operations. While the Cyber Dial Agent accelerates investigations and reduces context switching, Purview DSPM ensures that every interaction remains compliant, secure, and auditable. Together, they help SOC and InfoSec teams achieve: Faster Response: Reduced MTTD and MTTR through streamlined navigation. Stronger Governance: AI guardrails that prevent data oversharing and enforce compliance. Operational Confidence: Centralized visibility and proactive risk mitigation for AI-driven workflows. In an era where AI is deeply integrated into security operations, these tools provide the agility and control needed to stay ahead of threats without compromising compliance. 📌 Guidance for Success Start step-by-step: Begin with a pilot group and a limited set of policies. Iterate Quickly: Use DSPM insights to refine your governance model. Educate Users: Provide short training on why these controls matter and how they protect both the organization and the user. Stay Current: Regularly review Microsoft Purview and Copilot Studio updates for new features and compliance enhancements. 🙌 Acknowledgments A special thank you to the following colleagues for their invaluable contributions to this blog post and the solution design: Zaid Al Tarifi – Security Architect, Customer Success Unit, for co-authoring and providing deep technical insights that shaped this solution. Safeena Begum Lepakshi – Principal PM Manager, Microsoft Purview Engineering Team, for her guidance on DSPM for AI capabilities and governance best practices. Renee Woods – Senior Product Manager, Customer Experience Engineering Team, for her expertise in aligning the solution with customer experience and operational excellence. Your collaboration and expertise made this guidance possible and impactful for our security community.538Views2likes0CommentsApply Sensitivity label on SharePoint or Teams site to block offeline sync
Hi All, I was wondering is there any way if we apply a label toa SharePoint or Teams site (backed by SharePoint), we can enforce restrictions such as "Don't allow offline sync". Thanks in advance, DilanSolved103Views2likes2CommentsPeople of Purview: Elie El Karkafi
How long have you been working with Microsoft products? I am a Microsoft MVP in Security and a results-driven and dedicated Senior Solutions Architect with more than 14 years of professional experience in Microsoft Technologies. I have in-depth experience in Cloud, Security, Enterprise Mobility, Messaging & Collaboration, and IT Infrastructure. I am dedicated to customer satisfaction with focused delivery of technical solutions. I'm a proven leader in directing operations, maintenance, and support of complex systems. Highly adept in request for proposal development, technology needs assessment and staff training. How (and when) did you get involved in the Microsoft Community? (MCCP, MVP) Tell us about your journey! I became a member of the Microsoft Customer Connection Program (MCCP) in 2022 and was honored with the Microsoft MVP award in Security in 2023. Throughout my time in the MCCP, I’ve consistently contributed valuable insights and feedback to help enhance Microsoft Security products. Over the past years, I’ve been recognized as one of the top contributors across several MCCP focus areas—ranking second in Security, and first in Identity, Management, and Purview in the last two years. My contributions have earned me multiple accolades, including the Community Rockstar Award and Community Leader Awards in Security, Management, Entra, and Purview, along with several Partner of the Month honors. My engagement spans more than 150 private previews, 200 surveys, 50 focus groups, and 50 one-on-one feedback sessions with Microsoft product teams. I’ve been actively involved in shaping the future of AI and Microsoft Security Copilot, including identifying and resolving bugs in Copilot for Entra and Purview. As a Security Design Partner, I’ve collaborated directly with Microsoft designers on key features such as XDR Case Management and Microsoft Entra Conditional Access Optimization Agent. The MVP recognition not only validates my expertise but also enhances my professional credibility, supporting both client engagements and career growth. Being an MVP provides early access to Microsoft products and services, allowing me to deliver cutting-edge solutions. It also opens direct communication channels with Microsoft product teams, enabling me to influence product development and stay informed about upcoming features and roadmaps. What do you find most rewarding about being a community member? Being part of Microsoft Customer Connection Program (MCCP) significantly enhanced and diversified my skill sets in many ways: Product Innovation: Contributed to the enhancement of Microsoft products—specifically Defender, Sentinel, Entra, Purview, and Intune—by supporting the development of new features and improved functionalities. Community Empowerment: Actively supported peers in engaging with Microsoft Customer Connection Programs (MCCP), helping them amplify their impact through increased contributions and facilitating more direct interactions with product teams. Program Advocacy: Championed participation in Microsoft initiatives by providing strategic feedback and encouraging broader community involvement to drive continuous improvement. Collaborative Development: Partnered closely with Microsoft Product Groups and UX Designers, delivering in-depth user feedback to influence product direction and usability. Program Shaping: Leveraged personal experience within Microsoft programs to help co-develop and refine these initiatives in collaboration with internal teams. Tool Creation: Designed and launched a security calculator—originally built for internal use—which is now widely adopted by CCP members to assess and compare Microsoft security solutions and simulate associated costs. What advice do you have for others who would like to get involved in their Microsoft Community? To all Folks, look for opportunities to join programs like the Microsoft Customer Connection Program (MCCP), MVP program, or private previews. These give you direct access to product teams and a chance to influence development through feedback. Don’t be afraid to ask questions, share your experiences, or offer help. Even small contributions like answering a question or sharing a tip can make a big impact and help you build credibility Community involvement is a journey. Stay curious, keep learning, and show up regularly. Over time, your presence and contributions will be recognized!!! And the most important thing is to stay humble!!! Do you have anything you’d like to promote or recommend? (your blog or podcast, an article you recommend, a book everyone should read, etc) Security Calculator that I Built: Login - Microsoft Security Calculator Personal website where my blogs are posted : Elie El Karkafi - MVP - Personal Blog LinkedIn Page: (1) Elie El Karkafi | LinkedIn Credly Profile: https://www.credly.com/users/eliekarkafy MVP Profile: MVP Communities --- Elie is based in Dallas, Texas and is a Senior Solutions Architect at ampiO Solutions. (Listen.Develop.Deliver - ampiO Solutions) Banner photos (above) are from Elie's trip to Spain visiting Santiago Bernabeu stadium as he is a fan of Real Madrid football Team. ____________________________________________________________________________________ Stay tuned to meet more People of Purview! If you would like to get involved with the Microsoft Security Community, here are some quick actions you can take: Log in (here, on Tech Community!) and follow: The Purview Community - post questions, respond to community members The all-up Microsoft Security Blog Join the Security Community mailing list Join the Customer Connection Program Check out this Community Choice article for a comprehensive list of Microsoft Security Community offerings.464Views4likes0CommentsSafeguard data on third-party collaboration platforms
I am exploring options to safeguard sensitive data in third-party collaboration platforms like GitHub and Confluence. Does Microsoft Purview provide any native integration for these platforms? Do I need to rely on third-party connectors/integrations to extend Purview’s capabilities into these environments?77Views0likes1CommentCopilot DLP Policy Licensing
Hi everyone We are currently preparing our tenant for a broader Microsoft 365 Copilot rollout and in preparation to that we were in the progress of hardening our SharePoint files to ensure that sensitive information stays protected. Our original idea was to launch sensitivity labels together with a Purview data loss prevention policy that excludes Copilot from accessing and using files that have confidential sensitivity labels. Some weeks ago when I did an initial setup, everything worked just fine and I was able to create the before mentioned custom DLP policy. However, when I checked the previously created DLP policy a few days back, the action to block Copilot was gone and the button to add a new action in the custom policy is greyed out. I assume that in between the initial setup and me checking the policy, Microsoft must have moved the feature out of our licensing plan (Microsoft 365 E3 & Copilot). Now my question is what the best licensing options would be on top of our existing E3 licences. For cost reasons, a switch to Microsoft 365 E5 is not an option as we have the E3 licences through benefits. Thanks!Solved196Views0likes2CommentsMicrosoft deployment blueprint - Address oversharing concerns for your M365 Copilot deployment
Optimized deployment leverages advanced compliance and automation capabilities available in Microsoft 365 E5. This episode outlines how E5 customers can proactively secure data and enhance Copilot performance.1.5KViews0likes0CommentsColumn-Level Lineage Visualization Issue for Custom Entities and Processes in Azure Purview
I’m trying to implement column-level lineage for data assets and custom transformation processes in Azure Purview using the Atlas API. I have defined custom typedefs for tables (yellowbrick_table), columns (column), and a process type (custom_data_transformation_process), and I’m uploading entities with composition relationships and detailed column mappings. Although the generated JSON and typedefs appear to be correct according to the Apache Atlas documentation, I’m unable to get the column-level lineage to display properly in the Purview UI Specific Issues: 1. Missing 'Schema' tab in custom table entities (yellowbrick_table): When navigating to the detail page of a yellowbrick_table entity, the 'Schema' tab — where the contained columns should be listed — does not appear. 2. Missing 'Switch to column lineage' button in the lineage view of custom processes: In the 'Lineage' tab of a custom_data_transformation_process entity, the side panel titled 'Columns' displays "No mapped columns found," and there is no button or option to switch to column-level lineage view. This happens even when the columnMapping attribute is correctly populated in the process entity. 3. Error message when trying to edit column mappings in the process lineage panel: If I attempt to edit the column mapping in the lineage side panel of the process, I receive the error: "Unable to map columns for this asset. It's a process type asset that doesn't have a schema." (This is expected, as processes don’t have schemas, but it confirms that the UI is not interpreting the columnMapping for visualization purposes.) Context and Steps Taken: I have followed the Apache Atlas documentation and modeling patterns for lineage: Typedef column: Defined with superTypes: ["Referenceable"]. RelationshipDef table_columns: Defined as a COMPOSITION between DataSet (extended by yellowbrick_table) and column, with cardinality: SET on the column side. Typedef yellowbrick_table: Contains an attribute columns with typeName: "array<column>" and relationshipTypeName: "table_columns". Typedef custom_data_transformation_process: Extends from Process and includes a columnMapping attribute of typeName: "array<string>". Entities Uploaded (JSON): * Table entities include complete definitions of their nested columns in the columns attribute. * Process entities include the columnMapping attribute as a list of JSON strings, where each string represents a DatasetMapping with a nested ColumnMapping that uses only the column names (e.g., "Source": "COLUMN_NAME"). * I’ve tested with different browsers Despite these efforts, the issue persists. I would like to know if there are any additional requirements or known behaviors in the Purview UI regarding column lineage visualization for custom types. Specific Questions: 1. Is there any additional attribute or configuration required in the typedefs or entities to make the 'Schema' tab appear in my custom table entities? 2. Are there any specific requirements for the qualifiedName of tables or columns that could be preventing the column-level lineage from being visualized? 3. Could there be a known issue or limitation in the Purview UI regarding column-level lineage rendering for user-defined asset types? 4. Is there any way to verify on the Purview backend that the column composition relationships and the columnMapping of processes have been correctly indexed?" Annexes: # 1. Define the 'column' type # Ensure the superType for 'column' is 'Referenceable' typedef_payload_column = { "entityDefs": [{ "category": "ENTITY", "name": "column", "description": "Columna lógica para linaje columna a columna", "typeVersion": "1.0", "superTypes": ["Referenceable"], "attributeDefs": [] }] } # response = requests.post(typedef_url, headers=headers, json=typedef_payload_column) # print(f"Estado typedef column: {response.status_code} ({response.text.strip()[:100]}...)") # 2. Define the explicit relationship 'table_columns' # Ensure that the cardinality of 'endDef2' (columns) is 'SET' typedef_payload_table_columns_relationship = { "relationshipDefs": [ { "category": "RELATIONSHIP", "name": "table_columns", "description": "Relación entre una tabla y sus columnas", "typeVersion": "1.0", "superTypes": ["AtlasRelationship"], "endDef1": { "type": "DataSet", "name": "parentTable", "isContainer": True, "cardinality": "SINGLE", "isLegacyAttribute": False }, "endDef2": { "type": "column", "name": "columns", "isContainer": False, "cardinality": "SET", "isLegacyAttribute": False }, "relationshipCategory": "COMPOSITION", "attributeDefs": [] } ] } # response = requests.post(typedef_url, headers=headers, json=typedef_payload_table_columns_relationship) # print(f"Estado relationshipDef table_columns: {response.status_code} ({response.text.strip()[:100]}...)") # 3. Modify the table's typedef to use this relationship # Ensure the 'columns' attribute on the table points to 'table_columns' typedef_payload_yellowbrick_table = { "entityDefs": [{ "category": "ENTITY", "name": "yellowbrick_table", "description": "Tabla en Yellowbrick", "typeVersion": "1.0", "superTypes": ["DataSet"], "attributeDefs": [ { "name": "columns", "typeName": "array<column>", "isOptional": True, "cardinality": "LIST", "valuesMinCount": 0, "valuesMaxCount": -1, "isUnique": False, "isIndexable": False, "includeInNotification": True, "relationshipTypeName": "table_columns" } ] }] } # response = requests.post(typedef_url, headers=headers, json=typedef_payload_yellowbrick_table) # print(f"Estado typedef yellowbrick_table: {response.status_code} ({response.text.strip()[:100]}...)") # 4. Define the custom process type # Ensure the 'columnMapping' attribute is a string array typedef_payload_process = { "entityDefs": [{ "category": "ENTITY", "name": "custom_data_transformation_process", "description": "Proceso de transformación de datos con linaje de columna (Custom)", "typeVersion": "1.0", "superTypes": ["Process"], "attributeDefs": [ { "name": "columnMapping", "typeName": "array<string>", "isOptional": True, "cardinality": "LIST", "valuesMinCount": 0, "valuesMaxCount": -1 } ] }] } # response = requests.post(typedef_url, headers=headers, json=typedef_payload_process) # print(f"Estado typedef custom_data_transformation_process: {response.status_code} ({response.text.strip()[:100]}...)") example of generated json: [ { "typeName": "yellowbrick_table", "guid": "-105", "attributes": { "qualifiedName": "DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn", "name": "TBL8_CONOCIMIENTO_CLIENTE", "description": "Tabla origen: TBL8_CONOCIMIENTO_CLIENTE", "columns": [ { "typeName": "column", "guid": "-336", "attributes": { "qualifiedName": "DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn#CUENTA", "name": "CUENTA", "description": "Columna CUENTA de tabla tbl8_conocimiento_cliente", "type": "string", "dataType": "string" } }, { "typeName": "column", "guid": "-338", "attributes": { "qualifiedName": "DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn#TIPO_DOCUMENTO", "name": "TIPO_DOCUMENTO", "description": "Columna TIPO_DOCUMENTO de tabla tbl8_conocimiento_cliente", "type": "string", "dataType": "string" } }, { "typeName": "column", "guid": "-340", "attributes": { "qualifiedName": "DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn#IDENTIFICACION", "name": "IDENTIFICACION", "description": "Columna IDENTIFICACION de tabla tbl8_conocimiento_cliente", "type": "string", "dataType": "string" } }, { "typeName": "column", "guid": "-342", "attributes": { "qualifiedName": "DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn#NOMBRE_1", "name": "NOMBRE_1", "description": "Columna NOMBRE_1 de tabla tbl8_conocimiento_cliente", "type": "string", "dataType": "string" } }, { "typeName": "column", "guid": "-344", "attributes": { "qualifiedName": "DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn#APELLIDO_1", "name": "APELLIDO_1", "description": "Columna APELLIDO_1 de tabla tbl8_conocimiento_cliente", "type": "string", "dataType": "string" } }, { "typeName": "column", "guid": "-346", "attributes": { "qualifiedName": "DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn#APELLIDO_2", "name": "APELLIDO_2", "description": "Columna APELLIDO_2 de tabla tbl8_conocimiento_cliente", "type": "string", "dataType": "string" } }, { "typeName": "column", "guid": "-348", "attributes": { "qualifiedName": "DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn#GENERO", "name": "GENERO", "description": "Columna GENERO de tabla tbl8_conocimiento_cliente", "type": "string", "dataType": "string" } }, { "typeName": "column", "guid": "-349", "attributes": { "qualifiedName": "DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn#EDAD", "name": "EDAD", "description": "Columna EDAD de tabla tbl8_conocimiento_cliente", "type": "string", "dataType": "string" } }, { "typeName": "column", "guid": "-350", "attributes": { "qualifiedName": "DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn#GENERACION", "name": "GENERACION", "description": "Columna GENERACION de tabla tbl8_conocimiento_cliente", "type": "string", "dataType": "string" } } ] } }, { "typeName": "custom_data_transformation_process", "guid": "-107", "attributes": { "qualifiedName": "linaje_process_from_tbl8_conocimiento_cliente_to_tbl_tmp_clien_conocimiento_cliente_c@yellowbrick_conn", "name": "linaje_tbl8_conocimiento_cliente_to_tbl_tmp_clien_conocimiento_cliente_c", "description": "Proceso que conecta TBL8_CONOCIMIENTO_CLIENTE a TBL_TMP_CLIEN_CONOCIMIENTO_CLIENTE_C", "inputs": [ { "guid": "-105" } ], "outputs": [ { "guid": "-106" } ], "columnMapping": [ "{\"DatasetMapping\": {\"Source\": \"DB_DWH_EXTRACCION.HOGARES.TBL8_CONOCIMIENTO_CLIENTE@yellowbrick_conn\", \"Sink\": \"DB_DWH_STAG.CLIENTES.TBL_TMP_CLIEN_CONOCIMIENTO_CLIENTE_C@yellowbrick_conn\"}, \"ColumnMapping\": [{\"Source\": \"CUENTA\", \"Sink\": \"CUENTA\"}, {\"Source\": \"TIPO_DOCUMENTO\", \"Sink\": \"TIPO_DOCUMENTO\"}, {\"Source\": \"IDENTIFICACION\", \"Sink\": \"IDENTIFICACION\"}, {\"Source\": \"NOMBRE_1\", \"Sink\": \"NOMBRE_1\"}, {\"Source\": \"APELLIDO_1\", \"Sink\": \"APELLIDO_1\"}, {\"Source\": \"APELLIDO_2\", \"Sink\": \"APELLIDO_2\"}, {\"Source\": \"GENERO\", \"Sink\": \"GENERO\"}, {\"Source\": \"EDAD\", \"Sink\": \"EDAD\"}, {\"Source\": \"GENERACION\", \"Sink\": \"GENERACION\"}]}" ] } } ]192Views0likes1Comment