I don’t think it’s in the Android project, is it?
It was on the other screenshot you shared. Or maybe I’m seeing thigns…
Ah–I see. I have it installed in both.
Looks like this may be an issue with the “Live Player” app I was using to run it instead of an emulator.
oh yeah, LivePlayer == the suck. use the emulator.
I can’t because I don’t have the latest Windows update and I’m restricted by our work network.
Haha that sounds like a burn… but it isnt. #Ambiguity
Yes
Well–I have a phone, but no cables to get the package from A to B.
That’s what I was hoping the Live Player would do.
Zomg, it worked. <3
(Found a cable from a coworker)
ship it to my house aaron and i’ll update it for you!
Sure thing. Just give me your address.
@josecgomez Is this the proper way to add parameters?
//get
Dictionary<string, string> dic = new Dictionary<string, string>();
dic.Add($"expand", "PartWhses");
dynamic partData = EpicorRest.DynamicGet("Erp.BO.PartSvc", string.Format("Parts(ISI,{0})", part), dic);
The json object coming back doesn’t have the Part Warehouse expanded.
I think expand needs a dollar sign in front. (inside the quotes)
Also you can pass in the company ID using the CallSettings instead of that funky oData syntax (makes it cleaner IMO)
EpicorRest.CallSettings = new CallSettings("YourCompany", "YourPlant", "Yourlanguage", "YourformatCulture");
The last two can be empty strings
Is the oData syntax this Parts(ISI, S-160)?
So, if I set up the call settings would I then add this line to the dictionary to bring back the one part:
dic.Add($"filter", "PartNum eq 'S-160'");
Correct
Well hold on I thought you were using the ISI stuff to get the company there are SOME calls that do require params like the part number) However part doesn’t as far as I can tell