@rosenjon behavior = PrintItemLabel does not seem to be a right selection for recordAction. According to documentation valid values of behavior are: Cancel, Create, Delete, Open, Record, Save, SignReport and Void.
Hi @Dioris Aguilar -
I am trying to connect a button in the mobile app to a custom PXAction that I wrote in an extension library. There must be a way to trigger a PXAction from the mobile app that isn’t one of the stock actions, right?
Thanks,
Jonathan
@rosenjon For sure you can do that, probably you are not able to do it because you are assigning a wrong value to Behavior. Here you have a list and explanation for every valid value for this property: https://help-2022r1.acumatica.com/Help?ScreenId=ShowWiki&pageid=6d93c127-423c-4597-82c3-6f3fff4bf5ab
I’ve tried Void also. Didn’t change anything….
@rosenjon @Dioris Aguilar
Try to change
update container "HeaderView" {with
update container "StockItemSummary" {
Also confirm that you see the exact action name “PrintItemLabel” under Tools > Web Service > Service Description
@Fernando Amadoz Thanks for your reminder about checking the Web Service section.@rosenjon This ItemLookup screen actually has a dynamic data source:
Hence, the action should be defined as a graph extension of at least one of those graphs:
public class InventoryItemLookup_Extension : PXGraphExtension<PX.Objects.IN.WMS.InventoryItemLookup.Host>In this case, it seems enough to define it as a graph extension of PX.Objects.IN.WMS.InventoryItemLookup.Host.
And the mobile customization will be as follows:
update screen IN202520 {In order to make the custom action available in the mobile app:
Hi @Dioris Aguilar -
Thank you so much for this very specific example. I am not yet able to replicate what you have shown here, but this has gotten me a lot closer. Thank you for describing the specific graph extension that I need to reference in order to add my new method and have it be available to the mobile app code.
What both you and @Fernando Amadoz are pointing out, and was reinforced with the recent Coffee + Code on mobile app development, is that the mobile app appears to have a tight connection to the screen based SOAP API in Acumatica. So the methods available to the mobile app are those available to the screen based SOAP API.
The piece I’m still missing is when I create my graph extension as you have shown above (i.e. PXGraphExtension<PX.Objects.IN.WMS.InventoryItemLookup.Host>), how do I then make my printItemLabel method available to the SOAP API for that screen, in order for the MSDL for the mobile site to be able to reference it? The PrintItemLabel action is not available in the “Actions” section of my xml file location at: http://xmysitex.com/(W(1))/SOAP/IN202520.asmx?WSDL , so I assume that is the reason my recordAction code in my msdl is still not working….
Thanks,
Jonathan
This XML file does not appear to have any style information associated with it. The document tree is shown below.
@rosenjon Try creating a graph extension for the other graph mentioned in the dynamic data source (PX.Objects.IN.InventoryItemLookupHost) as follows:
public class InventoryItemLookup2_Extension : PXGraphExtension<PX.Objects.IN.InventoryItemLookupHost>
Yes...I already did that:
namespace AddToWMSOne minor difference between what you have and what I have is the object type referenced in the PXAction, but I think that doesn’t matter.
Otherwise, I really think the issue here is that my PrintItemLabel PXAction is not referenced by the WSDL file in the SOAP api reference. That is the thing I haven’t figured out how to do yet...
@rosenjon It seems there’s an error in the PXAction definition in your example:
For the PXAction, you need to define it as follows:
public PXAction<PX.BarcodeProcessing.ScanHeader> PrintItemLabel;Notice it uses PX.BarcodeProcessing.ScanHeader instead of InventoryItem in the PXAction for the graph extension PX.Objects.IN.WMS.InventoryItemLookup.Host .
@Dioris Aguilar With regards to that library (PX.BarcodeProcessing.ScanHeader), you seem to be operating with some special sauce that I don’t have. I am not able to reference that library from my Acumatica/Visual Studio environment.
@rosenjon That is for 2021R2, what is your Acumatica version?
Yeah I’m on 21.210.0030….so same I think. Maybe I haven’t activated some features in Acumatica?
@rosenjon Add this reference to your project PX.BarcodeProcessing.dll , it should be in the Bin/ folder of your instance.
I don’t have that PX.BarcodeProcessing anywhere on my system. I don’t know why, but I also don’t think the type of the PXAction really matters here. You even posted it a different way in one of your subsequent example posts in this thread:
public PXAction<InventoryItemLookup.Header> PrintItemLabel;What does matter is that this action gets added to the wsdl file for this page. Do you know how to do that?
@rosenjon The second example is a different graph extension. All PXAction should be defined with the type of the main DAC of the PrimaryView, otherwise they will not show up, so, you can’t put any DAC there.
First example is a graph extension for PX.Objects.IN.WMS.InventoryItemLookup.Host with main DAC PX.BarcodeProcessing.ScanHeader.
Second example is a graph extension for PX.Objects.IN.InventoryItemLookupHost with main DAC InventoryItemLookup.Header.
You sent a screenshot of this button being successfully added to the screen, so I assume you are actually building/running this code, right? If so, can you please post the output from this endpoint (obv. replace base url with whatever site you’re using)...
http://ec2-54-71-32-123.us-west-2.compute.amazonaws.com/AlaskanCopper/(W(1))/SOAP/IN202520.asmx?WSDL
Also, did you get it to work both ways, using either graph extension type?
P.S. I’m going to retry this method: public class InventoryItemMaintExtension : PXGraphExtension<PX.Objects.IN.InventoryItemLookupHost>
I had typos in my type definition….
public class InventoryItemMaintExtension : PXGraphExtension<PX.Objects.IN.WMS.InventoryItemLookup.Host>
@rosenjon Forgot we can attach files.
Here’s the customization
Ok thanks for posting that. Can you help explain this to me. Are both Graph Extensions/PXAction declarations required in order to make this work? Or did you extend both graphs because we weren’t sure which one would stick?
You said before: “Hence, the action should be defined as a graph extension of at least one
Maybe you can break down a little more what’s going on here, and how I would be able to figure out which graph to extend. Also, once it is extended, then it’s as simple as adding the reference in the msdl to the ReferenceAction and ReferenceActionLink (as you showed above)?
@rosenjon Honestly speaking, trial and error: it worked in one instance with the first graph extension only and in another instance with the second.
I appreciate all your help on this!
At the same time...
Honestly speaking, trial and error: it worked in one instance with the first graph extension only and in another instance with the second.
...
I’m not really sure what this means for the reliability and consistency of this code. Maybe some of the core devs from Acumatica can chime in here and help us understand what’s going on?
Honestly, this is one of the disappointing things about this platform. It is often the case that things that should be easy (because they are easy in most other coding platforms), turn out to be irrationally hard. We’re not trying to shoot the moon here. We’re trying to press a button in the mobile app that will perform the same (already working) custom action that occurs in the non-mobile app. It’s disappointing that we have to get super hacky to do that...
@Dioris Aguilar I finally was able to make my way through your example. I got hung up on referencing an assembly for PX.BarcodeProcessing.dll. I am including a screenshot of how to do that below. I am still confused why that assembly cannot be refefereced with a simple “using” directive in Visual Studio. I think maybe what’s happening in this mobile screen is that it’s referencing both the old and new WMS versions in Acumatica in a single screen. In most cases, the user has either activated the old or
I can honestly say that in 1,000 years, I probably would never have figured this out without your help, so I am extremely grateful for your patience walking me through this. At the same time, it’s kind of a “shame on Acumatica” thing for this being so obscure and non-obvious and at the same time totally undocumented.
Anyway, the result seems to work pretty well, even if the process to get there was somewhat obscure.
