I want to know that after exporting solution to azure devops repos can we edit the code or add new features to the solution from repo itself by adding few lines of code and also i am able to see only files in XML format.
Actually in power app while editing we have some visualization of things but how can you do it in repos while developing new features. Please suggest if there is an alternative.
Editing the exported files is currently not supported. You must edit from within the designers in the browser. For powerapps (canvas apps) specifically, there is currently not an offline editing story, but if it does become enabled in the future, you'll see it on the blog at: https://powerapps.microsoft.com/en-us/blog
There are ALM tools for importing, exporting , and working with Azure DevOps. See https://powerapps.microsoft.com/en-us/blog/announcing-general-availability-of-microsoft-power-platform-build-tools/
Update: We've just announced new tooling to support this:
https://github.com/microsoft/PowerApps-Language-Tooling
More here: https://powerapps.microsoft.com/en-us/blog/source-code-files-for-canvas-apps/
Related
I'm playing with Excel Add-ins, and I'm not a specialist, so having read the documentation, I still find it complicated to publish and install it.
Basically, all I did was the very basic Excel Add-in described in the documentation and now I'm trying to figure out how to install it in Excel.
I see everywhere that this is vrey simple, all you have to do is to upload the XML manisfest file, etc. but using Visual Studio, I chose publish via FTP and I get 3 folders in my website:
Content
Functions
Scripts
These are full of js scripts, but I don't see the manifest file nor the home.css, Home.js and Home.html
Isn't it possible to just upload the files with Filezilla to a folder? Which files?
If so, then how do I install the addin in Excel?
Thank you so much for helping!
The manifest goes to a different place than the files in the web application part of the add-in. Please see this article and the links in it for the details of how to publish the web application and deploy the manifest: Deploy and Publish your Office Add-in.
UPDATE 1/10/19:
Some additional information in light of the OP's comments:
Please start with this article: Office Add-ins to get an overview. You will see that there are two main parts to an Office Web Add-in: (1) The manifest and (2) a web application.
The manifest can be sideloaded or deployed using several methods. For more information on publishing options, see this node of the documentation: Publish.
The web application can be published/hosted using any method or platform that you want. We don't give instructions for most methods because this information is already available on the web. However, this article, Host an Office Add-in on Microsoft Azure, explains how to do it on Azure. I recommend that you try that method of hosting first. Note that in step 6, you edit the manifest to point to the URL of your web app. When you feel familiar with the distinction between hosting the web app and deploying the manifest, you can try an alternate method of hosting the web app. No matter which method you choose, you will edit the manifest in the same way.
Is there any way that I can create a template within forms to utilize for every user in the company?
For instance; let's say I have the Sales Order Screen (SO301000) and the Document Detail grid configured in certain way, that display different amount of columns than the default (either more or less columns).
For each user I want to use this template (and all the ones created) that I will apply when I add the new user.
I'l appreciate any guidance and help.
EDIT:
I provided answer for Form element ASP template below. Although reading your question again I think what you're trying to do would be more along the lines of automating grid column configuration. We call this feature Default Table Layout.
There's a feature request for it here:
https://feedback.acumatica.com/ideas/ACU-I-415
The feature has been shipped in version 2017R2 and is documented here:
https://help.acumatica.com/(W(1))/Main?ScreenId=ShowWiki&pageid=30f3229f-20f1-4055-9c03-e0fe3b37080d
Image copy of documentation page:
For ASP Form templates
There are two ways to work with customizations in Acumatica:
As a Customization Project, everything is done directly in Acumatica
instance through the web browser using the Customization Project Editor.
As an extension library (DLL file) compiled in Visual Studio which is then included in the FILES section of a Customization Project.
For method 1, I believe creating custom templates would be a bit of a hack and would not be officially supported, if someone knows otherwise please chime in.
For method 2, we ship the Visual Studio templates with the Acumatica Configuration Wizard (Acumatica ERP Installer).
Those templates are in the following folder:
My Documents\Visual Studio 20XX\Templates\ItemTemplates\Visual C#
The templates will be available for ASP.NET solution only. You can open Acumatica Instance Website as a solution if the website is already deployed:
When you open Add New Item dialog:
The Acumatica Templates will be available:
Those are standard Visual Studio templates so you can copy and re-use them to create your own. Microsoft documentation for creating user template applies and you can follow their guidelines. Note that working with Visual Studio and creating your own template is somewhat less user friendly than using Acumatica Customization Project Editor.
Acumatica T100 covers using Visual Studio to create customizations and would be a good starting point to learn the techniques involved:
https://openuni.acumatica.com/courses/development/t100-introduction-to-acumatica-framework/
Previously when provisioning list, libraries, site columns, content types, list definitions etc in SharePoint I typically used SharePoint features, deployed via a WSP - or used PowerShell scripts. This meant I had a package that could be deployed to DEV / TEST / PROD.
I'm working with SharePoint within Office 365 and unsure on the best way to provision lists / libraries / features within SharePoint.
Options:
No Code Sandboxed Solutions
Trying to avoid using these as the information from Microsoft on whether they are deprecated is flaky - however sandboxed solutions would allow me to deploy features with list definitions etc. I know sandboxed solutions with c# are definitely deprecated, but the info around no code solutions is poor.
Apps
I know apps can provision at both the app and host web level, but creating lists, libraries etc using the CSOM seems like a lot of effort and a step backwards.
PowerShell
The SP Online PowerShell is nowhere near as powerful as on-prem SP. I can provision site collections through this, but not lists or libraries...
I'm keen to know how other developers are deploying to Office 365, specifically around provisioning sites with specific list definitions, libraries, content types and so on...
Thanks
Microsoft did clarify the position on No Code Sandbox solutions - http://blogs.msdn.com/b/sharepointdev/archive/2014/01/14/deprecation-of-custom-code-in-sandboxed-solutions.aspx
Also if you are looking at using Powershell to deploy then you might want to go down the route of using CSOM from within PowerShell - SharePoint Client Browser for SharePoint 2013 is good for setting up a session also very good for viewing the content of a 365 tenant - http://spcb.codeplex.com/
I have been using code based provision for almost two years without any issues at all.
Server side model works just fine, CSOM has some limitation but stil cool one and JSOM could deliver the same feature set as both CSOM and SSOM, sorta 95% :)
PowerShell is not the best option as it hard to integrate into CI, put some unit testing and regressions.
As you mentioned, this is "step back", but if only you don't have any framework or foundation for that. My libraries are internal one, but there is SPGenesis at codeplex and SPMeta2.
As community don't really care, need or with such libraries for provisioning (yep, let's face it), there are much such libraries at all, but there are lots of "MVP" samples sorta "hello world" level.
Finally, what I would suggest is to invest your time and effort in code based provision.
This is a future, that's it ;)
UPD
Struggling with SharePoint's API inconsistency, bugs, "by-design" behaviour, unaffordable amount of time to write, support and upgrade WSP packages and XML, a team of passionate SharePoint professionals decided to come up with robust, testable and repeatable way to deploy such artifacts like fields, content types, libraries, pages and many more.
Enjoy and let us know how it goes.
SPMeta2 at GitHub
SPMeta2 at Nuget
SPMeta2 Documentation Wiki
SPMeta2 Bugtracker
I have data living on the cloud in table storage and I would like to move this down to a development server.
I used to use Clumsy Leaf table explorer but I seem to often have problems where not all the data is moved. It gives an error half way through when I try to import data that I exported from the cloud.
Are there other options for me to move data between one location and another?
By the way I notice this question was asked before but that was in 2011 and the suggested made does not work. Please don't vote to close this as I hope that things changed since 2011.
If you're looking for other tools, may I suggest you look at Cerebrata tools (http://www.cerebrata.com). You could either use Cloud Storage Studio or Azure Management Cmdlets to download data from the cloud and upload in development storage.
Hope this helps
A while ago, I wrote a blog post about the different azure storage and service management tools. Most of the mentioned tools are still valid and they probably improved since I wrote the post. Check it out at http://gshahine.com/blog/archives/2010/11/04/azure-service-management-tools/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I am now in the process of planning the deployment of a SharePoint solution into a production environment.
I have read about some tools that promise an easy way to automate this process, but nothing that seems to fit my scenario.
In the testing phase I have used SharePoint Designer to copy site content between the different development and testing servers, but this process is manual and it seems a bit unnecessary.
The site is made up of SharePoint web part pages with custom web parts, and a lot of Reporting Services report definitions.
So, is there any good advice out there in this vast land of geeks on how to most efficiently create and deploy a SharePoint site for a multiple deployment scenario?
Edit
Just to clarify. I need to deploy several "SharePoint Sites" into an existing site collection. Since SharePoint likes to have its sites in the SharePoint content database, just putting the files into IIS is not an option at this time.
I would also suggest checking out the SharePoint Content Deployment Wizard by Chris O'Brien.
http://www.codeplex.com/SPDeploymentWizard
Should help smooth the process you describe, and it's a nice tool for your kitbag regardless
We have a BizTalk 2006 with Web Application and Several WebServices that need to go from Dev to UAT to Live.
We use MSBuild right from within VS to build, run tests, dependent on test result, complie, zip and ship to servers.
Small MSBuild script on server to unzip, move the files, install clean web app, unlist biztalk bits, install new biztalk bits, re enlist and then start the stuff.
MSBuild is hugh and more people need to use it as it there now right in the platform =>
Use MSBuild
Note that "solution" has a specific meaning in Sharepoint: a collection of features (like web parts, list definitions and so on) packaged for deployment as a .wsp file.
You typically build sharepoint solutions in Visual Studio and package and deploy them using some tool like Sharepoint SmartTemplates http://www.codeplex.com/smarttemplates
However in your case you already have content in a live sharepoint site which you want to move to another site. It will probably be too cumbersome to use a solution for this, especially if you want to do it more than once (though it is possible to generate a solution from a live site using SharePoint Solution Generator).
The easiest way to deploy all content from one live site to another is to create a backup of the site using stsadm and then restore it to the new site again using stsadm restore. This completely overwrites the new site.
You can move select files/lists using import/export (rather than backup/restore). A tool like SharePoint Content Deployment Wizard makes it easier to select the content to move.