I have a couple of new fields in Sales Order (Screen ID - SM204505). I have added these fields from customization project > Data Access. Once published this customization project all the new fields are created in SOOrder table.
Now I want to reference these new fields in my Customization Project in Visual Studio to fill some other values (i.e. add some more business logic).
For example, there is a custom field called UsrReasonCode added to SOOrder table. And then I want to write some business logic to get this value from SOOrder and fill into some other table (i.e. Document Line item > ReasonCode)
It is working if I create Table Extension but I am not sure how to reference if I add it through DAC Extension. Please suggest.
You can reference extension fields by using extension object
like that:
DocExt ext=PXCache<Doc>.GetExtension<DocExt>(doc);
This will get extension object DocExt related to the original Doc object. So you can reference extension fields like ext.UsrField.
To read more about that you can download T300 training from acumatica university
Related
0
I have created a Document Set Content Type named "Contract" with 2 shared columns (Start Date, End Date). I have also created a Document Library named "Contracts" which use this content Type.
I have created a new contract "Contract 1" based on the "Contract" Content Type then I have uploaded a word document within the "Contract 1" Document Set, then a Edit form popped up asking for updating the Start Date and End Date properties but these 2 properties have already inherited the values of the document set's properties and I dont want the values of these 2 properties to be updated at the file level (I want them to be always the same as the values of the Document Set 's properties)
So I am asking you if there is a way to prevent the user from changing the properties values of the uploaded document, so that they always stay the same as the ones inherited from the document set which it belongs to.
Thanks,
Regards
As per my knowledge, there seems to be no OOB way to prevent this. You have to educate your end users not to modify the original metadata.
i have a situation where i created a new Table in Acumatica DB and i use de DAC Generator to create the class, i've chose the table and it shows no columns of the table, i've tried with other DB, another Acumatica Framework and it does keep showing no colums... any help ?
I would suggest creating the DAC using the Customization Project Editor instead.
Procedure:
1. Create new table in database
2. Reset the website (IISReset or go to page Apply Updates and use Restart Application)
3. Create a new customization project
4. Navigate to code section and insert a new code document
5. Use wizard to generate the DAC from the database table
I have created a customization which contains DAC extension. There are few extra fields added to Stock Item screen (InventoryItem table). After publishing, the customer had a requirements for one of the field to change its datatype from string to bool. I did updated in customization and published it. However, it did not updated in database. As a result it was throwing an error. Is there anything I am missing here? Please suggest.
Acumatica doesn't delete columns out of the database as a result of a change in your customization. You have two options here, you can drop the column via SQL command and publish, or more realistically, you can just create a new UDF with a different name and change your code.
I'm modifying the properties form of a SharePoint list that requires the user to select one or more items via a lookup to a document set. The document set library has a "Name" field which I cannot select as a field in my form's lookup properties.
The document set, of course, is a collection of documents grouped together with a common name, workflows, and metadata. The "name" I'm trying to display in my lookup list is set by the end user, but is inaccessible to me. Ideally, when someone is viewing an item in my SharePoint list (the one I'm trying to link from) and they see an associated document set item, they would be able to click on the name and it will take them to that element within the document set.
Any ideas?
Okay, I got around this issue by creating a new workflow that fires any time a record is modified. This workflow sets a new text field to the value in the Name field. To apply this to existing records, I created a new checkbox field named "Fire Workflow", then went to the Datasheet view and checked that checkbox for all of the records. This forced the workflow to fire on each record and update the new text field.
Now I just reference this new text field for the lookup in my other library. All is good!
We have a requirement for a site wide document library that contains simple word letter templates.
From within a customer item on a list we need to be able to select one of these templates and then have the template populate with customer data such as name & address etc.
What’s the easiest way to achieve this? Ideally without using workflows.
Then you shall assign a document template to a content type.
See this blog post, http://sharepointchick.com/archive/2011/01/07/using-content-types-with-document-templates-when-using-quotnew-documentrdquo.aspx
Create fields in your template that display the document properties to "Autofill" them. This is done in the Insert tab of the ribbon, then by clicking QuickParts, then Document Properties.
The end result is that in addition to the File > Info or the properties bar, each property will also appear in the body of the document wherever you have inserted the field for it. These can then auto-update themselves based on the metadata stored with the document in the library (how often they update is a Word setting).
Xpertdoc Letter Management for SharePoint let's user pick a template from the context of a customer record, then generates a new document with customer data automatically merged inside the document.
CGU, an insurance company, estimate they save 0.5 million dollars per year by the efficiency gains introduced by Xpertdoc. http://www.youtube.com/watch?v=xbqWiFt5dUA&feature=channel&list=UL.
First of all, you should use the technique mentioned before for the document creation based on content type.
As for auto-filling the property fields, I suggest you check out this post that explains how to auto-fill properties when document is added.
You can also opt for a commercial solution such as Harmon.ie for SharePoint to retrieve your templates. They have a free version, if I'm not mistaken.