We are updating our files
The BMW Coding Tool 2.50 allows you to update your SP-DATEN (Data files) automatically instead of manually installing the files by copy and pasting files.
We may choose to have no explanation in any document, but since documents aren’t required to have the exact same number of fields, we have this choice.
Before we begin querying related documents in our Azure Cosmos DB, we’ll add five more documents which follow similar structure to the documents that we updated – we can add these directly with the “New Document” option or through the Shell (I’ve formatted it for the Shell, but either will add the document): When we’re done adding the five documents, after refreshing the collection, we’ll see the total of ten documents – the _id field will differ in your Azure Cosmos DB, since this field is automatically generated: Next, we’ll query our database for our Treadmill Runs and we’ll notice that in our output we get a lot of fields that we may not want – such as the _id field and the type field (since it’s already being filtered for in this query).
Just like with selecting columns in SQL Server, we may only want to select some fields from a collection.
We created five documents in our Azure Cosmos DB and we’ll first start by updating these documents with numerical values for measurements so that we can compare them when we add data.
We’ll start by querying our first document by using our unique identifier of the date and time of our routine (datetime Routine) in the Shell that we’ll want to update. We first specify the unique identifier of our document – in this case the date and time of the routine – then in the next set of brackets, we update the existing document fields.Similar to a technique we use in SQL Server, with Azure Cosmos DB, we can update a document by first removing the document and adding the document again (notice how the _id field will change – which is automatically created since this is a Mongo DB API).