Azure Mobile Services: no data tab - azure

I am trying to create a simple table in Azure Mobile Services so that my c# Windows Phone App can utilize a high score table. However, though it appears in every example I find online, there is no "Data" tab inside my mobile service I created on Azure where I can create that table. They removed it or something, but there is no documentation whatsoever. Anyone know what's going on?
Thanks.

You probably chose to use a .NET backend (as opposed to JavaScript). When you do so, the DATA and API tabs are not visible in the portal. This is because both your data access and custom API's are part of your Visual Studio solution and have to be deployed from there. If you want to use the Javascript backend where you create your tables, APIs, and edit their scripts in the portal, you'll need to create a new Mobile Service and choose Javascript as the backend.

When you first create a mobile service, you won't have [any data in the] data tab. The easiest way to get started is to choose one of the sample app templates (iOS, Android, Windows Phone, Windows 8, HTML, Xamarin, PhoneGap). You should see an option then, to download the client app. There should also be an option to set up a default bit of data (the todoitem table). Once this is done, you should see the Data tab.
This isn't the only way to create data, but it's the simplest, especially when first starting out.

Related

How do I update a SharePoint list via REST API in a script ran on another server for Sharepoint 2013 an also Sharepoint Online?

I need to update data in a sharepoint list remotely via a script that runs on a schedule. We currently are using sharepoint 2013 foundation but will be moving to sharepoint online in 6 months or so. I would like to know how to do this via the REST api for both 2013 on prem and online versions. Im having a hard time wrapping my head around all the different auth models, sharepoint products, available apis, frameworks etc and when reading the documentation on MSDN I cant be sure which is relevant to what version of sharepoint etc.. Anyway, so far im thinking or the 2013 on prem sharepoint I should use the High-trust certificate auth option so my script is authenticated via a certificate. Do I need to create an add-in for script to register it as an app that will talk to the rest api? The reason Im not sure is sharepoint itself never really has to call on my script and its not a webpart or page or antyhing that gets displayed on sharepoint so im a bit lost.
As for how to push data into sharepoint online lists, im assuming I would then have to register the script as a providor hosted Add-in and authenticate using OAuth2 via Azure ACS server.
Does this sound like the best way to acheive my goal? Am I on the right track or is their an eaiser option? Is there anyway I can just use a Active Directory user account in the script to make authenticated requests instead of having to create certificates trusts and create addins etc?
Update:
Heres some more info on what I'm trying to do...
The project Id like to start will be a Node or PHP script that runs on a seperate server and pulls data from a third party source, making calculations on it and then pushes the results into some Sharepoint lists. Then running this on a schedule every night to keep the Sharepoint lists up to date. I know how to do everything except getting started with Sharepoint; how to establish the connection and authentication basically.
What id like to do is access the REST apis for lists and libraries from Node or PHP which would obviously be running externally to Sharepoint. I just don't really understand how to get started. My understanding is there is Sharepoint hosted apps (client side javascript that can access the SP apis), and provider hosted apps (which is essentially an iFrame to another web app). So out of the two I'm looking at provider hosted, but do provider hosted apps only run when called? Do they need to present a front end to show in an iframe? My project only needs to push data into lists overnight. And so do I need to register the project as a provider hosted app?? Or how do I go about getting started? And then I'm lead to believe that the app model is the 2013 way of programming for Sharepoint and the new 2016/online way is Sharepoint framework (SPFX). But then the only examples I'm seeing for this is client side apps. The second project id like to do is to make a client side app which will take the data thats in the lists from project 1 and display that in certain ways dynamically using react. So I'm fairly comfortable knowing where to start for project 2, ill just straight into developing a client side react app that uses SPFX. However I'm totally stuck on starting project 1. Where do I start for project 1? What are my options?
As far as I understand your question, You need to update your on prem list from schedular and later you will update the list in your sharepoint online.
We you can create a Provider hosted app and through configuration you can switch your destination easily.
OR you can think new way to do that. You can use Node JS timer service which insert to your on prem usign rest api later the same code will work for online you just need to change the destination.
Currenlty we are also donig it with Node. Below is the simple code to create timer in nodejs.
what is does, it read the crednentials from file and email to the user.It just a simple code and can be use to insert to SP list usign rest api.
https://github.com/halfice/Node-JS-Timer-SharePoint/blob/master/app.js
furthermore It would be more clarify if you could share picture of what you want to do

Can i create an old version of Azure Mobile Web Service

I have some pre-existing Azure Mobile Services, these were written when they were using request.service.mssql.query() when running a custom sql statement. However since then Azure has updated their mobile services to instead use req.azureMobile.data.execute()
I need to create a new Azure Mobile Service that connects to another database. This new service uses very similar calls to the existing services I already have running.
Is there a way for me to create a new Azure Mobile Service that is using the old method? Because if I must use the new method I will have to re-write the calls which is a lot of work as there are lots of calls.
If I must use the new method, is there a fast way to convert the pre-existing calls to the new method?
Thanks
There is a compatibility NPM to allow your Mobile Service scripts to run in a Mobile App. It also requires a view of your database with different system column names for the createdAt, updatedAt and deleted columns. Or if you don't have an existing Mobile Service using the old column names, you can just rename the columns (remove the __ prefixes).
The Azure documentation has a more complete page on upgrading your Mobile Service using this NPM.

Published custom .NET Backend broke Azure Easy Tables

I was following the Microsoft Azure documentation to integrate my Xamarin Forms app with azure mobile services. I defined a data connection, used easy tables to define some custom tables and everything was working as expected with the mobile client.
Today I wanted to extend my backend functionality and also enable file storage. I followed the instructions found here and as soon as I created a new .NET server backend project with a StorageController and published it to azure, the entire easy table api stopped working. All calls from the mobile client fail with the following error:
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
This happens for all mobileClient.GetTable<SomeEntity>().SomeOperationAsync() calls.
My guess is that publishing the custom backend overwrote the online generated easy tables api... unfortunately I don't have enough experience with the azure cloud to figure out where I made a mistake. Is there any way of getting the auto generated easy tables api to also work with file storage?
As Mimi noted in the comments, Easy Tables is only available for the supplied Node backend, deployed from the portal. If you are using your own code and publishing that, Easy Tables and Easy API will be disabled.

Azure Mobile APP with Easy Table and Easy APIs gives error "Unsupported Service"

I have created mobile app and wanted to use Easy Table and Easy APIs. However whenever I go to that location it shows "Unsupported Service".
Below is the image link of my azure account console.
Thanks in advance.
Easy Tables and Easy APIs are (currently) only supported for Node (Mobile Apps or Migrated Mobile Service) applications, not for .NET applications.
Please see the following thread for more details https://social.msdn.microsoft.com/Forums/silverlight/en-US/07ee8c8a-a2fc-47ad-aca4-2ec4b5e8ac4a/enabling-mobile-extension-for-your-app-runs-forever?forum=azuremobile
You can use Easy Tables with a .Net backend. I ran into the same problem following the Quick Start steps posted by Microsoft. What you want to do is delete your application in the portal, create a new one, setup the database, then click Easy tables. It will initialize for you using the database you created.
Do not click on any Quick Start links.

Get Azure Dashboard data via api

Scenario:
One team had built one application, and application is running on azure.
maintenance is taken care by same team, we don't want to give full access of production instance to developer team, but want to give read permission, like - monitoring of logs, cpu usages etc.
Solution according to me is build an application which will get dashboard data and log data from azure via api and that data will be displayed to development team.
I am referring these 2 links
https://msdn.microsoft.com/en-us/library/azure/dn722415.aspx
https://azure.microsoft.com/en-in/documentation/articles/api-management-get-started/
Question:
Still I am not able to find api which will give the dashboard data. if anyone know api for the same, please help.
Is there any alternative solution for this scenario.
If you deploy your app using the new Azure Resource Manager mode, it provides a Role Based Access Control to your resources. You can deploy your app inside a Resource Group and provide read access to your developers. They will be able to view the information about the services that your app are made of but without the option to change anything.
This session from Build 2015 can help you to understand what ARM is and what you can do with it: https://channel9.msdn.com/Events/Build/2015/2-659

Resources