How can i drop a collection with assest inside ? delete is disabled (screen). thank you
You will have to delete those assets inside of the collection before the delete options will be enabled.
Either manually via the UI or programmatically via the REST API or PyApacheAtlas delete the eight assets in the collection.
You may have to also delete all of the scans related to the collection as well which can be done via the UI or REST API as well.
Related
I have enabled SharePoint online integration with Dynamics.
It creates folder as and when I navigate to Documents Tab.
My question is how to create these folders for already existing Records. I do not want to navigate to each of the records and then click on Documents tab and then let CRM/SharePoint create folder.
Is there any trigger which I could do programmatically so that folder will be created automatically.
Note: I can create SharePoint Document location record per hand orprogrammatically but then I would be needed to give Folder name as (<Record Primary Name><Record Guid>) which I would like to avoid.
Reason: SharePoint and CRM does neglect special characters which are not allowed in SharePoint and I do not want this headache of looking for correct name. I want CRM/SharePoint to perform just it should happen for already existing records.
Any Idea?
I was using on-demand workflow in similar situation. You can try with creating of on-demand workflow with step which would create document location. Here you have nice guidelines.
Image source
I setup a demo instance of Azure Search with the web front end app.
One thing I have noticed is that even after I remove a document from Blob storage and the indexer runs again, the deleted document and its contents are still stored in the index. How can I remove the document’s contents from the index without deleting and recreating the index?
Here is the link to my GitHub repository for the template for this environment… https://github.com/jcbendernh/Azure-Search-Ignite-2018-Demo
Any insight that you can provide is extremely appreciated.
In order to get a document to be removed from your index by the indexer when it is no longer in the data source, you need to define a data deletion detection policy in your indexer.
There are two different approaches:
1. By defining a column that defines which fields are supposed to be deleted from your data source (SoftDeleteColumnDeletionDetectionPolicy)
2. Or by using the new native soft delete support in blob storage (NativeBlobSoftDeleteDeletionDetectionPolicy)
Both of these approaches are documented at https://learn.microsoft.com/en-us/azure/search/search-howto-indexing-azure-blob-storage#incremental-indexing-and-deletion-detection
Thanks,
-Luis Cabrera (Azure Search PM)
I'm creating a mobile app backend with Azure App Service. I created a database connection to an existing sqlserver db. However, when I clicked on the Easy Tables blade there were no results of the current table. How can I use the existing tables with this mobile app? Thanks
OK i figured this one out .. make sure the app connection string is correct, then go ahead and add the table to the easy tables list (like a new table), it will pick up all the existing columns in the table automatically!
Be careful: It also messes with the table structure adding deleted and roversion etc columns in azure style. It doesnt seem to delete anything though
I have created a Mobile App and Database in Microsoft Azure. Now I am trying to create Easy Tables from Mobile App but I am getting error message "You need database to use East Tables. Click here to create one.
Even though I have existing database Easy Tables doesn't list it.
Below is the screenshot.
I have mapped Data Connection with mobile app, below is the screenshot
It would be great if anyone can help, I am new to azure.
Your connection string must be created with name: MS_TableConnectionString
Just because you have a database doesn't mean it is linked. Click on Data Connections, then Add, then add your existing SQL database.
Note that Easy Tables won't recognize the existing tables unless you add them through Easy Tables. There are notes around the format of Id (it needs to be
a string) and other fields.
When you created your Database Server did you check "Allow azure services to access server"? That could be why you cannot see the Database listed.
I am using Azure search and would like to make sure I can recover from a self inflicted disaster before I push more docs in there. How do I backup my index?
Is creating Azure Search replicas equivalent to making a backup?
How would one restore that?
Thanks
Microsoft have released a console app on github that can be used to backup and restore Azure Search Indexes - its not perfect, but I use it almost daily for backup and restores from prod to CI/QC/Dev instances
https://learn.microsoft.com/en-us/samples/azure-samples/azure-search-dotnet-samples/azure-search-backup-restore-index/
Right now you can't do that from the API or the portal, just save a copy of the JSON schema to a .js file, for example. See the Get Index API.
Normally you don't need to touch the index very often, only add, update or remove documents.
You would need to use an indexer from an external source to push the data into Search and be able to create backups at the same time.
If its an AzureSQL database, this may do it for you automatically, depending on your subscription
Create a table with the same fields in the Azure Search Index and add a deleted flag and a last update date, then import all of your data into the database. Set the date flag to the time that you imported the data.
At the top of the azure search bar, there is an option to 'Import Data'. This will allow you to connect the data source, this way you can create an index which will look at the last modified data and deleted flag when you create the connection.
The wizard will take you through all of the options
From there, just update the SQL table with your changes and the indexer will automatically push them to Azure search.
Thank you for an answer about https://learn.microsoft.com/en-us/rest/api/searchservice/Get-Index
Sometimes Azure Search index it's an only source to restore data.
For example in Microsoft QnA maker - if you will delete azure web app or azure app service- you no longer can even export Knowledge base from QnA maker.
To somehow restore data from QnA maker- I used Azure Search index.