One of my clients (state public defenders office) has asked me to write a system to update people's (laywer's) calendars (google for govt, calendar) on a daily basis, from data pulled from the Circuit Court (a seperate agency) via web services. Currently the defenders office is using Visual Studio 2001 beta for most of their applications, but will allow me to develop something new in VS2010 and SQL Server 2008 r2. Currently, they pull data from these web services and put them in a SQL Server database, to enable displaying this info on their web site.
I can't seem to find any demo, nor source code, in Dot.Net, to connect to Google Calendar as an administrator, and insert calendar events about upcoming case and trial appearences.
Another agency (The District Attorney's office) has written an application to pull data from the aforementioned web services and create calendar events in MS Exchange and MS OutLook. It is hoped that the defender's office can do the same with Google for Govt.
The network admin there told me to look at GAM (python app). I'm hoping to find C Sharp examples rather than try to translate Python to C Sharp, line by line.
Randy
Check out the official Google Calendar API!
There are client libraries for .net
It also has a get started section on the .net download area. You'll probably need access setup before hand to make the changes though.
Related
i'm working with xamarin forms and i would like to implement notifications in my app; but i can't see the push option on my appcenter. I don't see the option :
I went to the documentation; but it says in the option 3 In the project navigator that opens, select Push.. i'm confused! Thanks.
AppCenter is (unfortunately) retiring its push notification service. They recommend migrating to Azure Notification Hubs (which are slightly more complex, but also more powerful).
You can refer to this Announcing MBaaS Service Retirement on
February 3rd, 2020 by John Wargo from Principal Program Manager, Visual Studio App Center .That is an official announcement.
Earlier last year, we launched the App Center Auth and Data services in early preview. Together with App Center Push, the three services form the App Center Mobile backend as a service (MBaaS) offering, and give developers an easy entry into using Azure as a backend for mobile apps.
As a result, we are discontinuing efforts in the Auth, Data, and Push services and working to retire these preview services in App Center. With this change, we will focus App Center on delivering a world-class mobile and desktop DevOps experience. We will also work together with Azure teams to help migrate developers to the native Azure services, and ensure that Azure continues to be a great platform for your mobile apps.
What This Means to You
Your apps can continue to use these services for now; we want to give you ample time to consider, and implement other options for your apps before we retire the services.
May 3, 2020
After this date, the Auth and Data services will no longer be available in the App Center portal; the services may continue to operate for a short while after this date, but you will not be able to interact with either service using the App Center portal UI.
App Center Push Retirement Timeline
Microsoft is committed to providing the best notification offering possible and we think the best way to do this is to focus our efforts on a single offering in Azure Notification Hubs. We know many of you value the unique features unique to App Center Push and we want to offer similar capabilities in Azure Notification Hubs. With that in mind, we’re working to create a transition plan which causes the least disruption to our existing customers as they move to Azure Notification Hubs.
Hopefully, someone can straight up my PowerApps connectors understanding. Apparently, I have 3 connection options.
Common data service - this connection type only allows me to connect to CDS 1.0 databases, but I want to connect to an existing D365 v9 instance.
Common data service (experimental) - this connection type asked me for a D365 v9 instance ID, but everything is grey out after the step, i.e. it didn't show me any entity after connecting successfully.
D365 data source - this one works but I was told MS has stopped working on this connector. Also, I will have to update the connection after deployment to a different environment manually.
What is the best practice if I want to use a CDS connector? Or I will be stuck with the old D365 connector for now?
Thanks.
==11/1/2018 update==
I have a better understanding of my situation now. Every Dynamics 365 CE instance should have a PowerApp environment automatically, but one of my D365CE instances doesn't. I am suspecting it is because the D365CE instance is still version 8.2.
My question above is because I created an empty PowerApp environment and tried to connect it to the D365CE instance (v8.2). I will give you guys another update after I upgrade the instance to v9.
==11/30/2018 update==
Confirmed. By upgrading a D365CE instance from v8.2 to v9.0, the Power Platform generates an environment automatically and linked it to the D365CE/CDS.
Here's a breakdown of the three connectors you're looking at :
Common Data Service - this connector actually supports both versions of CDS, but it will be dependent based on the environment that you're in. So if you're in an environment that has a CDS1.0 database, it will connect by default to that environment. If you have a CDS2.0 database, it will connect by default to that environment.
Experimental Connector - this is similar to the previous connector, but it includes experimental features in development by our team, and isn't recommended for production use. Generally you should only be using this connector if there is a specific feature we announce in the experimental connector you wish you use.
Dynamics 365 Connector - this is similar to the base CDS connector, however it can only connect to CDS2.0 environments. It also has the ability to connect across environments. So you can be in Env1, but connect to a database in Env2. The normal CDS connector will only connect to the database within the environment you are building your app in.
Which one should you use? The Common Data Service connector is going to be your best option, it's where the most improvements are being released at the moment, and is designed to work best with PowerApps and Flow.
To connect to your Dynamics 365 environment, you'll want to make sure you start from web.powerapps.com and select that environment from the drop down in the top right, if you can't find your Dynamics 365 V9 environment - make sure you have system customizer permissions - if you do and you still can't see it, it may be an issue on our end. You can send me a message with your Dynamics org URL and we can check it for you.
Once you can select it from the environment drop down, you can then create a new app and use the Common Data Service connector, and it will connect directly to your Dynamics 365 data.
Hope this helps,
Clay.
I don't have much experience with CDS 1.0 in the Power Platform. I can share some insights on my experience with Microsoft Flow / Logic Apps, CDS 2.0, and Data Integration. So I hopes this helps add another perspective to this question too.
What is your goal in using Common Data Service? Just to pull Dynamics 365 CE data into it?
This recent Product Team Blog could be useful here if so.
Some initial feedback, if the main goal is to connect to a Dynamics 365 CE instance, consider using the Dynamics 365 Connector through Microsoft Flow. You can create a small Flow at https://flow.microsoft.com/ with a 2 step process like mine below. An event takes place in Dynamics, like creating an account. The event and it's data is captured and in used in a response process, like sending an email alert. In this case the alert is sent to the signed in users email.
From a developer standpoint you can also use the Xrm SDK and Web API to collect data and do some data processing as well in C# or JavaScript respectively too. This is more involved, but provides a greater amount of control around the data you're working with. There's a great intro to
Lastly you can spin up a PowerApp to surface your data as well with some pre build templates https://create.powerapps.com/.
Start with your Data and create a Dynamics 365 app in a phone layout.
Choose your organization and table.
After the app creates, hit play to run it.
Search for an account
It turned out the problem is not with the connectors but with PowerApp environments. By upgrading a D365CE instance from v8.2 to v9.0, the Power Platform generates an environment automatically and linked it to the D365CE/CDS. So, it should just work for all v9+ instances.
I have a MS Access Database that I need to share with multiple users in the entire state. Right now I split the database and placed the backend on a shared network drive and distributed the front end, but the issue I'm having is that offices further away can't enter a record in a timely manner (one office took over 2 hours).
We do have SharePoint, but it's on a 2010 server and our MS Access is 2013 and I'm told because of this, access won't link up to SharePoint and this is not an option.
Someone in my office mentioned something about replicating a database...is this something that will work? If not, are there any suggestions?
Replication in Access was killed in Access 2007.
SharePoint is not an option except if you start from scratch, and the shared lists and/or various web apps you can create are seriously limited compared to your present desktop solution.
Basically, you have three options:
Upgrade your WAN to 100 Mbit/s low-latency quality fibre connection
Create a Terminal Server hosting your application. Remote users will access this via standard Remote Desktop Connection
Upgrade your backend to SQL Server Express (free) and set up an in-house or outsourced server hosting this
The first options require zero coding, while the last takes a little but not much, and that is well documentated (just bing/google on this).
I am builing a Windows Phone Store App at the moment and I am planning to build a Windows Store App in the future (Universal Windows App). I want to synchronize the items stored in the local SQLite database with a remote database and between the different platforms (Windows Phone, Windows, ...).
So, I did a few searches about mobile backends and I ended up at Microsoft Azure App Services for Mobile with offline sync. Before I start, I want to clarify some important questions for me.
I have different users which will authenticate via Facebook, Microsoft Account, etc. How will the different entries be distinguished for each user? Do I have to add an userId property on each table and select only entries with relation to the userId?
I am currently using the NuGet package sqlite-net with sqlite-net extensions for support of relationships like One-to-Many, Many-to-Many, etc. Azure Mobile Apps seems to support only simple objects and I have to manage the relationship via a foreign key manually.
How much will Microsoft Azure App Services for Mobile Apps cost for a few thousands user, if I only use the remote database with offline sync?
I'm not sure this is the correct way but yes. Then you can customize the PullAsync to return only records that relate to a specified user (https://github.com/Azure/azure-mobile-apps-net-client/issues/181).
Yes. Currently it does not support relations for the client SQLite database. You have to do it manually in your client. Have a look at Adrian's answer here: (Offline Data Sync in Azure Mobile Apps with Views or Stored Procedure)
It depends on your data and the database type. If you are using Azure SQL Server, a basic plan with a monthly fee of ($5 to $10) may be good to go. And for the Azure Mobile App you can start the free plan.
Background:
ETL on source data from Excel, Access, Sql Server '8, .txt files.
Data Cloud is created
Dashboard is in progress
I have searched online because I remember seeing a marketting demo video by QlikView that it's possible to share the dashboard among other users. Not just a snapshot image or pdf. The real dashboard as a working file.
If client pcs receive a link to connect to the same data cloud via web - that's easy.
But what I want to know, is it possible to package and "port" the entire working file with underlying data to another person? (I am not asking for zipping!)
Depending on if you've purchased a license for Qlikview, there are several ways to approach this... Best case scenario for you is if you and the client you want to send the .qvw to both have Named licenses, you can just send them the file and they'll be able to open it in their licensed Personal Edition. I'm imagining this is not the case since you mentioned they are clients and not colleagues within your organization.
You need to know that if the client or you do not own licenses, you will not be able to share a working version of your dashboard with them.
The common implementation would be purchasing Qlikview Server Software and then deploying a Qlikview server in the cloud that would handle incoming web requests and provide clients with an access point from which to access your dashboards (and underlying data). This solution requires you (or your company) to have purchased a set of licenses from Qlik as well as Server software.
You can review Qlik's license structure here. You may also want to review their End User License Agreement to make sure their model works for what you are trying to do.