I need to differentiate the recipient of Notification for every changes made on Task screen based on new custom field (Type).
My problem is that this new custom field can't be found when configuring condition on Automation Notification
Please help, how to enable this new field to be available for use as condition parameter on Automation Notification configuration.
It would be helpful to have more detail on your code for the extended field and the subject you are using for the Automation.
I have tested this successfully with extension libraries, so you may need to convert your extension project into an extension library.
This means you would need to compile the extension code into a DLL but it should work with what you need.
You can find more info in the Acumatica reference site:
http://help.acumatica.com/(W(1))/Main?ScreenId=ShowWiki&pageid=a3278167-2285-4c92-8404-367952b42d9e.
Related
We are currently in the process of a much needed upgrade from Acumatica 2019R2 to 2022R1 and are running into some questions that we are unable to locate information for. At some point in between the versions the workflow engine was created and also extracted the actions away into extensions in CRCreateActions.
Is there documentation anywhere that explains this new process? From what we can tell, if you want to customize these actions and override a method that the extension did not override you must create your own action extension and go from there. This then means you must also extend the worflow extension in order to swap out the action in the workflow. This feels like we are going down the wrong path.
What is the correct approach to extend what used to be ConvertToBAccount but is now called CRCreateBothContactAndAccountAction?
I'm having an issue, I created a custom table, added it to my customization project as a new DAC. The code is there, but how do i call this in a graph? I tried instantiating it as its own object, tried performing a pxselect, creating it as a viewname. None have worked for me, I looked through the documentation for "Generating a Data Access Class" And that doesn't apply to the ERP framework i get errors trying to generate class via that process.
Any ideas on how i should implement the new DAC to be accessible in my graph?
Thanks!
Found the solution, I incorrectly called my PXselect initially.
public PXSelect<UsrKSPOReceiptWeightSplit> WeightSplits;
Take your extension class from the AppRuntimeCode folder and cut/paste to your VS project folder. From there you can access your custom fields etc. Today in the Acumatica framework this is the procedure until this is fixed in the future. In the T300 manual this is covered in detail.
Here's a summary:
1. In Customization Mgr - create your data extensions
2. In VS copy the files that CM creted to your project to get a reference
3. Compile your extension library
4. When publishing your project you will have to delete your Customization extensions because there will be duplicates when you created your extension lib in VS.
I am using Orchard v.1.10.0.0
I need to update custom user field after he is created.
workflow decision activity is missing
How do i do that without it?
Solved by enabling module - "C# Scripting - Provides C# compiler services."
I have a request from the customer that they want every time they create a subsite (publishing site) .We have to add a custom column to OOTB Documents list.
I have done some researching the way to add the custom column to
Documents list in onet.xml but have no luck .
Then i think about the work around solution that i create a
ScriptBlock custom action that will call javascript function which
will add the custom column to document list , then i will put this
custom action to a feature ,and finally i will reference that feature
in onet.xml.
It run well but the javascript function call every time i refresh the page. I just want it run one time when i active the feature.
Does anyone have any suggestion ? I use sandbox solution and Sharepoint Online .Sorry for my bad English
I don't think a custom action is the right way to do this, Custom actions generally need some sort of user interaction.
Get CKS dev tools in Visual studio
Create a new SharePoint solution
Add a new web template(CKS Dev) to your solution from the Add new item menu in VS
Create an additional feature (web) with a list template (Your documents Library and add your column)
Update the Web templates onet file
Also sometimes it's better to put up what your having issues with as you have said you have had no luck with the above, What is the issue you are having, Post some code up etc rather than going down the route of changing the way you implement the solution
Many Thanks
Truez
In my solution I have a workflow where one step contains a reference to Queue. After importing this solution on another CRM instance this workflow could not be activated because it contains an invalid reference - Queue can not be resolved. Queue with same name is created on new CRM but resolving is probably based on record Guid.
Now, I'm wondering, is there a way to edit workflow steps using CRM SDK? Whole process of CRM solution deployment is automated. And I want to remove all manual work. Some example would be great :)
Thanx in advance!
There are 2 things you can do if you are having issues with the Guids not matching in a workflow lookup when deploying from one environment to another.
Use the API to create those records referenced in the WF. When you create a record you can actually specify the Guid that it uses as the id. So write a tool or see if one exists already that will create some default data for your environment.
Use a configuration entity with references to all the EntityRefrences needed in your WFs. Then you can create a custom workflow activity to retrieve the configuration entity record (there should only ever really be one) that contains all the references in that environment.