Updates to Assets Prevent Future Scan Updates

%3CLINGO-SUB%20id%3D%22lingo-sub-1977766%22%20slang%3D%22en-US%22%3EUpdates%20to%20Assets%20Prevent%20Future%20Scan%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1977766%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20been%20working%20with%20Purview%20slowly%20over%20the%20last%20few%20days.%20Today%20I%20was%20able%20to%20scan%20some%20heavily%20used%20on-prem%20SQL%20server%20databases.%20Once%20the%20scan%20was%20complete%20I%20went%20into%20the%20assets%2C%20located%20the%20first%20asset%20I%20wanted%20to%20classify%2C%20and%20started%20to%20add%20a%20description.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20minute%20I%20clicked%20Edit%20on%20the%20asset%20a%20warning%20appeared%20stating%20%22%3CSPAN%3EMaking%20a%20manual%20update%20to%20the%20asset%20will%20prevent%20future%20scans%20on%20this%20asset%20from%20updating%20it.%22%20As%20a%20software%20developer%2C%20I%20understand%20why%20this%20might%20be%20necessary%2C%20however%20as%20a%20member%20of%20the%20data%20governance%20team%20it%20concerns%20me.%20I%20need%20the%20ability%20to%20add%20classifications%2Fglossary%20terms%2Fcontacts%2Fdescriptions%20to%20newly%20discovered%20assets%2C%20but%20I'd%20also%20like%20scanning%20to%20update%20the%20schema%20as%20the%20asset%20changes%20based%20on%20information%20found%20in%20scans.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIs%20the%20functionality%20to%20edit%20an%20asset%20manually%20and%20receive%20updates%20from%20scans%20something%20that%20is%20on%20the%20roadmap%3F%20Will%20it%20be%20available%20in%20GA%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1977766%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Edata%20curator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Epurview%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eroadmaps%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EScanning%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1981352%22%20slang%3D%22en-US%22%3ERe%3A%20Updates%20to%20Assets%20Prevent%20Future%20Scan%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1981352%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F898204%22%20target%3D%22_blank%22%3E%40a_kanczuzewski%3C%2FA%3E%26nbsp%3BYes%2C%20this%20is%20something%20we%20are%20actively%20working%20on%20enhancing%20and%20supporting.%20We%20are%20looking%20to%20make%20granular%20asset%20update%20behavior%20updates%20in%20the%20first%20quarter%20of%20next%20year.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2138399%22%20slang%3D%22en-US%22%3ERe%3A%20Updates%20to%20Assets%20Prevent%20Future%20Scan%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2138399%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F890261%22%20target%3D%22_blank%22%3E%40VishalAnil%3C%2FA%3E%26nbsp%3B%2C%20please%20can%20you%20provide%20an%20update%20on%20when%20you%20expect%20this%20functionality%20to%20be%20available%20-%20we%20have%20the%20same%20concern.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2146203%22%20slang%3D%22en-US%22%3ERe%3A%20Updates%20to%20Assets%20Prevent%20Future%20Scan%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2146203%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F890261%22%20target%3D%22_blank%22%3E%40VishalAnil%3C%2FA%3E%20-%20love%20to%20get%20an%20update%20on%20this%20or%20if%20you%20can%20point%20me%20to%20a%20current%20roadmap%20for%20Purview%20that%20would%20be%20great%20as%20well.%3C%2FLINGO-BODY%3E
Occasional Visitor

We've been working with Purview slowly over the last few days. Today I was able to scan some heavily used on-prem SQL server databases. Once the scan was complete I went into the assets, located the first asset I wanted to classify, and started to add a description.

 

The minute I clicked Edit on the asset a warning appeared stating "Making a manual update to the asset will prevent future scans on this asset from updating it." As a software developer, I understand why this might be necessary, however as a member of the data governance team it concerns me. I need the ability to add classifications/glossary terms/contacts/descriptions to newly discovered assets, but I'd also like scanning to update the schema as the asset changes based on information found in scans.

 

Is the functionality to edit an asset manually and receive updates from scans something that is on the roadmap? Will it be available in GA?

4 Replies

@a_kanczuzewski Yes, this is something we are actively working on enhancing and supporting. We are looking to make granular asset update behavior updates in the first quarter of next year.

Hi @VishalAnil , please can you provide an update on when you expect this functionality to be available - we have the same concern.

Hi @VishalAnil - love to get an update on this or if you can point me to a current roadmap for Purview that would be great as well.

@a_kanczuzewski @VishalAnil Also interested for any updates on this. Do we have any news as per the above?