I was asked to create a new maint page where data could be added. Just like in the T100 series part1:Maintenance pages. Immediately a few issues arise, why in the Acumatica ERP project I am unable to complete the steps done in the Framework application? I tried to add a new item -> PXgraph option(as described in the instructions) was not available, I couldn’t even add my own c# class from scratch the option was not listed. Instead it just listed page options(will add screenshots below). I attempted to create a new .cs file outside the scope of the project and import it into the file and it wouldn’t recognize it as an available file to import. In the end I attempted to manually drag and drop the file into the Objects folder I wanted the file to be a part of.
VERSUS ERP Add new item
Secondly, I created a new ListView in the page. I was not able to choose my Typename:SO.SOusrPhoneExtMaint.cs file from the list of options. I have rebuilt the project numerous times to see if that was the issue. I manually added the TypeName by going into the source of the aspx and typing it my graph. When I tested the graph I got the following errors that “Invalid type PX.Objects.SO.SOUsrPhoneExtMaint specified for datasource.” My question is why is there a discrepancy between the framework and the erp application for customization and how do I customize the graphs and pages if they don’t take the same approach as the TXX development guides. If I am doing something fundamentally wrong I'd like to know what is the right approach.
I recommend that you use the Customization Project Editor for any customization of Acumatica ERP.
To add a custom form, perform the following actions:
Navigate to the Customization Projects form (SM204505; System > Customization > Manage)
Select an existing customization project or create a new project by clicking "+" on the form toolbar
Click the project name to open the project in the Customization Project Editor
On the navigation pane of the editor, select SCREENS to open the Customized Screens page
On the page, click ADD SCREEN > CREATE NEW SCREEN to open the Create New Screen dialog box
Fill all the required fields and click OK to obtain workable template of your custom form
The New Screen wizard creates the form template and includes it as the following items in the customization project:
two File items - .aspx page code for the new form
a Code item - code template for business logic controller
a Page item - the link to the new page content, which you can further develop by using the Layout Editor
a SiteMapNode item - the site map object of the new form
(For an example see Lesson 11: Creating a Custom Form of the T300 Acumatica Customization Platform Training Guide)
Further you can develop the items by using the tools you prefer.
The custom form will be added to Acumatica ERP after the project is published.
Related
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/
I need to create few templates for E-commerce site. Can anyone guide me as how to create templates in Kentico 9 ? There is an existing site and I need to create five other templates for the same. Am totally new to Kentico.
Please help.
There are many generic templates in Kentico, so you could clone any of them and modify to your needs - this might be easier for you to edit existing one as you'll have an example.
I'd recommend you to take following steps:
Go to Pages application in Kentico administration
Select any page in content tree on the left
go to properties -> template
Save as new template (so you do not screw up exting one) and save your changes
Switch to Design tab - this is where you build/configure you template
On the Design tab there is green line with template name and hamburger menu, where you can choose edit layout - this is where you can implement markup of the page as well as split your page into zones. After you accomplish html for you page save changes and close current dialog.
Now you should be back to Design tab. Here you can add web parts to zones you've specified in the layout. There is huge amount of different web parts (user controls). All they have different purpose and settings, so you should check documentation and figure out which one should be used in your particular case.
Try editable text, editable image, repeater, navigation in order to get an idea how it works.
I'd like to ask if you came up with a solution that will allow for subsites to access a centralized document library at the parent level. I'm still trying to no avail. I've tried doc library templates, views, Doc Center and the best method i have OOTB is a page view web part on the subsites page display a view from the parents library. (by the way to remove the ribbon, append ?IsDlg=1 to the url and the ribbons hidden) cool tip. Say will you give be a Y/N on a solution that will allow one to keep a set of documents in the doc center and surface them in the sub-site.
There are another option without such hard coding. You can open any view of your document library, as mentioned earlier AllItems.aspx for example with SharePoint Designer. Open it for editing in advanced mode (there are option when you click right mouse button on file in SP Designer). Then just point mouse cursor inside web part and chose in ribbon web parts, Add to Site gallery, see the picture. Fill in name of new web part. That is all, now you can add this web part on any page on any web site from webpart gallery through the user interface or through the SP Designer by clicking Insert, Web Part in the ribbon on any page.
You can do this by editing the AllItems.aspx (or other view page) and scraping off the WebPartPages:ListViewWebPart and pasting it into a page on the subsite.
This will give you an error "List does not exits The page you selected contains a list that does not exist."
Then you need to get the WebID for the root site (where you took the ListViewWebpart from and replace the part of the webpart that looks like this:
<WebId xmlns="http://schemas.microsoft.com/WebPart/v2/ListView">00000000-0000-0000-0000-000000000000</WebId>
with (for example)
<WebId xmlns="http://schemas.microsoft.com/WebPart/v2/ListView">7b04dee8-b120-4dee-abea-28b77316ec7d</WebId>
How can I Add a custom Ribbon group to an existing OOB Sharepoint Ribbon tab at run time?
I have a custom web part and I want to add a custom group to Ribbon.Documents Contextual tab at run time.
You need to provision tab definition using custom actions, and then in you server code use SPRibbon.MakeContextualGroupInitiallyVisible and SPRibbon.MakeTabAvailable to show up you tab.
Also you can use CKS.Dev extension for visual studio it contains templates which have some markup and code to help you to start.
You can use Javascript to create buttons. Here is the helpful link
http://www.ro.umt.com/blog/2013/11/14/creating-sharepoint-ribbon-elements-in-javascript/
if you look at the createTab() function you see you can create new group using this function CUI.Group .
I'm using MOSS (SharePoint 2007) and InfoPath 2007.
I have a Form Library with an attached InfoPath form, and would like to create new items (forms) in this library during a workflow built in SharePoint designer.
I've tried using the "Create List Item" action, but it doesn't assign the correct metadata (the new item looks fine in a view of the list, but can't be used to render the form (the generic "form has been closed" error comes up if you try to view the item)).
I'm not adverse to writing my own custom WFA to do this in .NET if need be, although it'd be nice to find a simpler solution.
Can anyone provide any resources for how to achieve this in SPD, or programmatically? My searches on the topic so far have been unfruitful...
Found the solution to this, thanks to a video on YouTube: http://www.youtube.com/v/bcnC_XwCcAg&hl=en&fs=1&rel=0
For anyone else out there who (like me) might not be able to watch YouTube content where they need this information, here's the process:
Create IP form
Publish to SP Server (as doc lib)
On document library, change settings:
allow management of content types
display in browser
"Fill out" a blank version of the form and save it to the doc lib with name "template"
Open context menu for "template" form and select Download a Copy
Delete "template" form from document library
Open library in windows explorer
Open Forms dir
Paste downloaded copy of "template" form into the Forms dir (as template.xml)
Go back into doc lib settings
turn off management of content types
change template url to template.xml
press OK to save changes
Go back into advanced settings ago, and turn management of content types back on
In SPD, make a WF which uses Create List Item to put an item in that library
And that's it. Just 12 steps needed to publish an InfoPath form so that it behaves as you'd expect, and any SharePoint developer should be familiar with 12-step programs.