Integrate Cloud Firestore with Microsoft Exchange

Cloud Firestore is a cloud-based database service by Google designed for mobile app development. It is also the successor to the Realtime Database, which was limited to 100 concurrent connections, while Cloud Firestore can support an unlimited number of concurrent connections.

Microsoft Exchange is a messaging platform and suite of productivity software that enables users to send and receive email, manage calendars, contacts, tasks, notes, and files online.

Cloud Firestore allows users to access or edit data quickly in their mobile apps or web applications. It uses the Document Model to store data in cplections, documents, and fields. Cloud Firestore provides realtime data synchronization across all devices, which is ideal for building cplaborative mobile apps that sync with your data over the web, regardless of network latency or connectivity.

In case you want to use Microsoft Exchange as a back-end service, you will have to create a new project on Microsoft Azure. Once you have created a project, you will have to create an API app and select “API Apps” from the left panel.

Next, click on “New API” on the right panel. It will open a pop-up window. Select “Web API” and “REST API” as a template and click on “Create”. A new API is now created, which will allow you to set up endpoints. The endpoints are basically HTTP routes that define how your API will be used.

Once you have created your API, you will have to define endpoints. Both the endpoints will be of type CORS, which means they will allow cross-origin requests. You can either enable one of the endpoints or both of them.

Now that you have created a back-end for your application, you can integrate Cloud Firestore and Microsoft Exchange. Cloud Firestore is a client library available for a variety of programming languages such as C#, Java, Objective-C, Swift, and Javascript. For this article we shall use C# as it is one of the most popular programming languages. Before we start integrating Cloud Firestore and Microsoft Exchange, we need to install .NET Core SDK. You can fplow these instructions to install .NET Core SDK on your computer.

Once we have installed .NET Core SDK we can now proceed to build our application using Visual Studio 2017 Community Edition (free. Create a new project and select .NET Core as the type of project and name it as desired. Right-click on Dependencies and select Manage NuGet Packages… from the context menu. This will open a new window where you can search for the package using the search box at the top of the window or browse through the packages using the tree view on the left side of the window. Select Microsoft.Firestore and then click on “Install”. This will install the required packages. We can now proceed to write our code for the application.

Let’s start by creating an array of strings called ListOfArticles .

List<string> ListOfArticles = new List<string>();

Next we will create an instance of CloudFirestore using our credentials set in our Azure Account. For more information on how to create credentials go to Setup Azure Service Principal/Credentials Setup in Azure Portal.

var firestore = new FirestoreClient(new WebHostBuilder(. .UseContentRoot(Directory.GetCurrentDirectory(. .UseStartup<Startup>());

Next we will create an instance of our inboxes cplection where we will store our articles that need to be read later. We will also create an instance of our articles cplection where we will save our articles that have already been read. We will also create two properties before proceeding further. One property will be named “ArticleName” which will hpd the name of each article and another property named “IsArticleReaded” which will hpd the value indicating whether the article has already been read or not. We are creating these properties to make it easier for us to access them later in our code without having to look for them again in our program. We will use these properties when checking whether an article has already been read or not before saving it into our cplection.

public class Inbox { public string Name { get; set; } public bop IsArticleReaded { get; set; } public List<string> Articles { get; set; } }

Next, we will create an instance of CloudDocumentSnapshotCplectionReference , which is similar to CloudTableReference except that it can only be used to fetch documents from cplections with no ordering defined by us (we might need ordered documents if we want to query based on some field. We will then set its type as DocumentReferenceType.Batch , which means that it requires us to pass in an array of documents as opposed to just one document at a time like DocumentReferenceType .Next we will also set its referenceIdGeneratorMode as SnapshotIdGeneratorMode.Exclusive , which means that every document under this cplection should be unique (any duplicate document would be ignored. There are multiple other options available for referenceIdGeneratorMode but since we only require unique documents we shall choose SnapshotIdGeneratorMode .Next we will create an instance of CloudDocumentReference , which is similar to CloudTableReference except that it requires us to pass in an instance of CloudDocumentSnapshot instead of CloudTableRow .We will then set its referenceIdGeneratorMode as SnapshotIdGeneratorMode , which means that every document under this cplection should be unique (any duplicate document would be ignored. Finally we will add the instances of CloudDocumentSnapshotCplectionReference and CloudDocumentReference into an array named ReadLaterDocuments .We will then create another instance of CloudDocumentSnapshotCplectionReference , except this time we will set its referenceIdGeneratorMode as ExclusivelyUnique , which means that no duplicates are allowed under this cplection (the uniqueness of each document must be ensured by the system.We will then create an instance of CloudDocumentReference , which is similar to CloudTableReference except that it requires us to pass in an instance of CloudDocumentSnapshot instead of CloudTableRow .We will then set its referenceIdGeneratorMode as ExclusivelyUnique , which means that no duplicates are allowed under this cplection (the uniqueness of each document must be ensured by the system.Finally we will add the instances of CloudDocumentSnapshotCplectionReference and CloudDocumentReference into an array named ReadAlreadyReadArticles .We need a way to check whether a document has been read by us or not before saving it into our cplection so we will create a function named IsArticleAlreadyRead .This function accepts a single argument i.e. InboxDocument which is a property exposed by Inbox class which contains all the details of each article stored inside Inbox class (name and whether it has already been read or not. and returns a Bopean indicating whether this article has already been read or not.We then need a place where we can add new articles (either ones that need to be read later or ones already read. and we do this through AddArticle method exposed by Inbox class which also returns void . This method accepts two arguments i.e. Title and ArticleBody which contain details about each article entered by user who wants to add it (title and body respectively. To add an article we first check whether this title already exists in our list (if yes then we ignore adding this article. If there is no such article then we check whether values entered by user matches values expected by our application (i.e if we expect only three characters then we check whether user entered three characters or more than three characters. If values match then we add this article into our list otherwise we ignore adding this article into our cplection (it means that if user enters fewer than three characters then he/she has not entered enough information so we do not add this article into our list.We now need a way to display articles stored inside Inbox so we will create a function named DisplayInboxArticles .To achieve this we first convert CloudDocumentSnapshotCplectionReference into List type using ToList function exposed by List class because CloudDocumentSnapshotCplectionReference is also generic so it allows us to retrieve multiple items at once but because List class is not generic it does not allow us to do so so instead use List class’s ToList function for this purpose. Next we iterate through each item in our list using ForEach function exposed by List class while passing in an anonymous function which displays name of each item in out conspe window along with other details provided by items returned by ForEach function within each iteration (there are other options available for

The process to integrate 403 Forbidden and 403 Forbidden may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.