So I've been tasked with getting a custom item field value displayed on an item in the cart of a site-builder site.
I have experience with SCA but not so much when it comes to site builder. I can see how templates are put together and how to display data in these templates.
I can also tell that it is possible to add or remove field sets from the cart in the 'Set Up Website' tab.
Another thing to note is that the Live Hosting Files are empty.. which is where I would have expected to find the scripts that would create the cart.
So my question is, how do I either create a new row in the 'Set Up Website => Cart' tab to display this new custom field. Or where can I find and edit the template/script that creates the cart?
Any help is appreciated!
Is this the old SiteBuilder Cart or from the new SiteBuilder Extensions? If so, which version? The old, original SiteBuilder Cart is really difficult to add customizations such as a custom field. I would do it by running an AJAX call on a SuiteScript to get the needed data that write it into the cart cell. It was a hack but at least I was able to customize it.
The SB Extensions work a lot like SCA, and it what to do depends upon the version. If it is only for the cart, then just extend Item Keys Mapping and then it will be available on the template file. If you also need it on the cart summary in the checkout then, see SuiteAnswers for the specifics for the various versions.
I am having the following inconvenient when inserting a
custom field on a DAC extension, with Acumatica 17.202.0016 and
18.103.0022 version. In both versions I followed the next steps:
1) Created a "Usr" field "UsrCustomString", on the Opportunities page
CR304000, followed by creating its controls and publishing
the customization project.
Creation of "UsrCustomString" field
2) Then I selected an existing Opportunity and assigned a value in the new field.
Updating record with new value
Checking in DB the updated value
After doing this, I noticed that after navigating
to the next record and then selecting back the
OpportunityID "OP000368", the custom field shows blank. The same happens after pressing the cancel button.
Field is shown blank
I tried this sequence in the Cases page "CR306000" and it worked
correctly. It seems an issue related to the CROpportunity DAC.
Definition of the DAC extension with "CustomString" value
The solution that #cbetabeta, worked well for me. Here is the link for the solution
Custom field on CROpportunity doesn't display saved value since upgrading from 6.10 or 2017R2 to 2018R1
version: 5.20.1752
I have created one custom dropdown control on contact form CR302000, the control looks good on screen, but the value of the control can't be saved (no error, but just nothing is saved), nor loading data from database.
I also have a custom textbox on that screen ,saving and loading the value of it both are working okay.
here is DAL code for dropdown:
[PXStringList(new string[] {"1","2","3"}, new string[] {"EN","FR","BI"})]
[PXDefault("1")]
[PXUIField(DisplayName="Language")]
What should I do to make custom dropdown to work?
Thanks
You can delete your column from the table manually using your preferred Db mgmt tool (eg. SQL Management Studio). Or if the client is hosted, you can create a SQL script which drops the column from the table. Then publish that SQL script.
Since you use version 5.20, consider building an extension table and DAC extension, for your user field. You can find the details to create them in the Acumatica T300 course.
Jeff is correct. You need to use the proper declarations - PXDBString, not PXString. What is the name of your DAC that you work with? Make sure it is not a PXProjection.
My question is : When I assign me a record as shown in following screenshot:
I want to stay in the form of the record and not go back to the list of records.
How Can I do it, do you have any idea?
Unfortunately there isn't a configuration available to change the behavior of the dialog box.
Create a cloned Assign to Me Button in the Command bar, and have it tied to custom javascript to create a SOAP request to assign the current record to the current user.
I'm trying to work out a way to display the contents of the version column from SharePoint (i.e. the value that changes every time a file is checked in) as a field (or something similar) inside of a Word document.
Ideally, I'd like to know how to configure SharePoint so I could click something like "Insert > Quick Parts > Document Property > Version", and it would include the version in the document. The goal is to make it easier for someone to correlate a printed version of a document with the version history of SharePoint.
I have been able to add editable text columns to the Document content-type and have them show up as document property quick parts. I've also been able to add a calculated column which gets the version as a text string... however this calculated column isn't showing up in Word as a document property. (Perhaps I'm missing a setting on the calculated column)
This is one way to get the version in your document, it's a bit painful to get it working...
Enable versioning and content types on your document library.
Go into document library settings and select the content types you want the version to appear in.
Select Information management policies settings from the content type menu.
Select define a policy and click .
Click on the 'Enable Label' Check box
Do not Check the other two boxes in the Labels section.
In the Label Format field, enter the metadata fields in the following format:
Version : {Version} \n
Set the label appearance and click on preview.
Click at the bottom of the page.
Go back to the library and create a new document using the content type you have modified.
Save the file as a Word 2007 format.
Select the insert tab
Select Quick Parts from the Ribbon menu and hover over document property
Select Label from the properties list
This should display the metadata defined in your label as a field in your word document. The field will update automatically when you next open the document.
Save.
This requires configuring both SharePoint and your Word document.
TO CONFIGURE SHAREPOINT'S DOCUMENT LIBRARY:
Go to the document library where you plan to store your version-controlled documents.
Click on Settings > Document Library Settings
Click on "Versioning settings" and make sure that you're either having it "create major versions" or "create major and minor (draft) versions".
Click OK.
Click on "Information management policy settings"
If your library can handle multiple content types, you'll see a list of them. Click on "Document". If it can only handle one content type, skip this step.
Select "Define a policy..." and click OK.
Check the "Enable Labels" box, but don't check either of the other two boxes in that section.
Type {Version} into the "Label format" box.
(Optional) You can format the version label.
Click on the "Refresh" button to see a preview of your version label. It will say something like {_UIVersionString}
When you're satisfied with the label's appearance, click OK.
To get back to your document library, click on the document library's name in the breadcrumb trail at the top of the page.
TO CONFIGURE YOUR WORD DOCUMENT:
Either create a new document in the library or upload one.
Open the document and edit it.
Put the cursor wherever you want the version label to appear.
Go to Insert > Quick Parts > Document Property > Label
The version label "{_UIVersionString}" will show up in the document.
Save the document (and choose what the next version should be). You're all set!
If you want to test it, close the document and reopen it. The updated version will automatically appear where you put the version label.
These instructions were based on Erwin's answer.
I followed Rachel's instructions and they worked great. However, capturing this version update in the document does create a problem if you want to do electronic signatures. For instance, if your version is 1.6 and you decide this is the one for people to sign; you'll find that when they sign it, the document will be saved as version 1.7. When you open the document again, the version 1.7 will not match the authorized version of 1.6 and you'll be informed that all the signatures are invalid.
IMPORTANT:
In SP2010 you cannot save as a site template when Labels are enabled within a document library under Information management policy settings. The document library will get corrupted and even if we disable the policy, the save as site template function is still broken. The only option seems to be to permanently delete and rebuild the list.
The RevNum field that I think jaloplo is referring to is not the same as the SharePoint document version number. It updates every time you save the document, but seems to keep its own revision numbering system, correlated to (but independent of) the SharePoint version numbering system.
Try creating a calculated field in a custom content type. The field can be equal to the Version. That will give you the ability to add it as a property in the document. This only works well with Office 2007 docs.
Once a custom content type is created, you create a new document based on the content type.
After creating the document, you can extract the document information panel and save it. It is an info path form, so you can customise it if necessary and upload the customised panel to the content type.
Erwin's answer is spot on, but I wanted to leave this in case someone runs into the same issue I did. If you attempt to set the label for version on the site collection content type rather than at the document library level, you will get the error "The label reference, Version, could not be found." when previewing or saving the Information Policy. Also, you will be unable to save a policy at the document library level if you have previously defined one at the site collection content type level. It must be set to "None" on the site collection content type. Probably should have been obvious to me from the start, but it wasn't, and maybe this will help someone else down the line.
All columns of a document library are document properties for a word document. To take the version of the document you have to show document properties and then select "advanced properties". In thit moment, you'll see the classic document properties window and you can see the "Version" property in the last tab.
So, you can add the value of this property to your document in the place you want, for example, the footer.