I'm wanting to create a project and add tasks to that project using Power Automate. Using the Common Data Service connector, I can create the project successfully but not the tasks. When I run the flow, I get a "Resource not found for the segment" error for the Project ID. It is the correct ID. What am I doing wrong?
There are two ways to create a new project, you can use Microsoft Project's "Creates new project" or you can use SharePoint's "Send an HTTP Request to SharePoint"
There are a two ways to create a new task in Microsoft Project Online (PWA). You can use Microsoft Project's "Create new task" or SharePoint's "Send an HTTP request to SharePoint."
You have to checkout the project and then check it back in. (Please note that the refresh time isn't instant. See here)
PWA is part of Microsoft Project Server 2013.
Related
I am using VS 2019 and web app is asp.net. I have signed into my Azure/Microsoft account through VS. When I tried to publish the app, I got the screenshot below. Somehow the "Next" button is greyed out so I cannot move forward to create my publish profile. By the way, I am learning Azure and using the free App Service Plan now.
You need to create App Service：
see: Publish your web app.
Here is what happened. To associate with Azure, a Microsoft account is linked to an Azure Directory. When I sign into Visual Studio with the Microsoft Account, the link is supposed to established automatically. But somehow it was not for my case. In Visual Studio, open "Personalization Account" page, click "Apply Filter" link, the next scene is where I can select which directory to be linked. I had only one directory but somehow it was not checked. Once I checked it, I am able to publish.
I've finally gotten around to familiarizing myself with Azure. I've created several App Services on a new App Service Plan. I've created a SQL Server instance and a SQL Server DB. My intention is to create new MVC sites, one for each App Service I created. I got the Azure SDK all set up and went about trying to create my first site, but now I'm stuck. It seems Microsoft expected me to create the projects in Visual Studio first, and allow the Azure SDK to create a corresponding App Service in Azure for the new projects. This isn't what I've done. So, I've encountered a screen where Visual Studio is asking me to put in details (Web App Name, Resource Group, App Service Plan) for the new App Service, but it doesn't let me choose from a list of existing App Services.
How can I associate the project I'm creating in Visual Studio with the existing App Service I already created in the Azure Portal?
This is the dialog I encountered while creating a new Web Application in Visual Studio and selecting the option to host in Azure. Notice there's a text box to enter a new App Service (Web App) name, but no drop-down to select previously existing App Services.
Azure Web Apps can be created in either direction. You should be able to create them either via Visual Studio or directly in the Azure Portal.
I'm assuming that you've already performed the following steps:
In Solution Explorer, right-click web app project.
In popup menu, select "Publish"
Select Azure subscription to see if any Web Apps exist.
From here on forward, you should be able to create a new Web App or select an existing Web App. Since you're not seeing your existing Web App, let's try to troubleshoot.
In the Publish dialog, create a new Web App (in Visual Studio).
In the Azure Portal, check to see if that Web App was created.
In case you have more than 1 subscription (e.g. free, BizSpark, MSDN from work), this will confirm whether you're looking at the same subscription in both places.
I've included a screenshot below to show you that I have multiple subscriptions, each of which contains a different set of Web Apps.
Hope that helps!
The product I’m trying to create a package out of is a Web Application and a Database Project. This Package needs to be deployed to multiple IIS Web Sites which individually has their own application pool and bindings. In the end I would want the package to be built by a TFS Build Server into a .zip file which via msdeploy.exe somehow can be deployed to these web sites by settings the web site, application pool, binding and destination database in deploy time. It should create if items does not exists and update if they do.
I’ve been researching quite a lot on Web Deploy 3.0. Most of the stuff I find on the internet via google is about defining the package and publishing from within Visual Studio which is not exactly what I want because I want to be able to have control over the settings at deploy time.
So far I can create a package relatively simple via the Publish dialog in Visual Studio 2013. I can even add my SSDT project dacpac file to the package using the “Update Database” checkbox in the Publish window. But I think a lot of things happen behind the covers which doesn’t seem logic how to do manually.
Ultimately the questions I have right now which I hope someone can help me with is:
How do I define dbdacfx settings in deploy time when deploying a
package? (Ie. Target sql server, database, username and password.) Or
can I parametrize these settings somehow into a parameter.xml file?
Can I use the publish profile xml file from my SSDT project?
How do I make my package create a new web site if it does not exists?
I can only find information about creating applications under already
existing sites.
When and if I create a web site via the package, how do I define the
associated application pool? Like creating it if it doesn’t exist or
update it if the target framework is incorrect?
I’ve read about providers. For instance appPoolConfig provider but
how to utilize this at deploy time isn’t very clear to me – can
anyone elaborate or perhaps point to a source explaining it?
Is there any good books covering this area or perhaps even a better
alternative?
i have an project with name called(dbservice layer) which is in path: d:\webservice\DBService. here i have an webservice which connects to DB and returns an object of an class.
once i added an reference here i get an url:http://localhost:2371/Jobs.svc
now i have another project name (UILayer) whic is in path: E:\School\UILayer
i added an service reference here with url as http://localhost:2371/Jobs.svc
but i get an messgae telling service is unable why is that happening.
if both my webserivce layer and ui layer are in same project. then i able to use the webserive in the ui layer. and get the required output
so i wanted to know is there any way we can acesss the webserive from one project to another project
thanks in advance
prince
Publish your web service to an actual location and then add a reference using the actual URL not the one served up by visual studio. What I think is happening is each Visual Studio instance is using a different port so you can't say localhost:2371 for both projects because that is the local port for the instance your running with your original project.
Publish it and then access it via http://localhost/jobs.svc. You should be able to access it via IE directly without running Visual Studio if you have published it correctly.
The main point is, you have the wrong URL.
From within FlexBuilder3, I can go to "Data/Manage Web Services..." select a web service, and click "Update" to ensure that my code and the server are in sync. How do I automate this so that each time I build, the automatically generated web service code is regenerated?
If the server interface changes during development but my code doesn't, it won't work anyway - I'd rather have a compilation error than a runtime error I had to track down to a changed web service interface.
Unfortunately you can not update a web service at build time. The update is part of the wizard and is not implemented as a separate action to be called on demand.
One suggestion I have is to go in the project properties and inside the Build panel add as a new builder a program. You will have to create this program that checks each time the project is build that the WSDL file did not change. It is a little bit complicated but if you are working on a project that relies on a web service that is under heavy development it might save you a lot of time.