Home
|
Forums
|
Contact
|
Search
|
Syndication
[login]
[create account]
Friday, November 22, 2024
slxdeveloper.com
Home
Search
Contact us
About slxdeveloper
Syndication
Community
Forums
(NEW!)
Newsletter Archive
Members
Your Profile
Submit Article
General
Administration
(6)
OLE DB Provider
Miscellaneous
(2)
Architect
VBScript
(9)
ActiveX Controls
(6)
How To's
(14)
.NET Extensions
(3)
External
OLE DB Provider
(12)
SLAPI (SlgxApi.dll)
SalesLogix COM
(1)
Web
ASP/ASP.NET
(2)
Web Services
Web Client
Downloads
Samples
(17)
Documentation
(7)
Utilities
(18)
Resources
SalesLogix
(3)
Programming
(1)
11/22/2024 8:55:38 AM
slxdeveloper.com Community Forums
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Architect Forums - SalesLogix .NET Extensions
Forum to discuss the use of .NET Extensions in SalesLogix version 7 and higher. View the
code of conduct
for posting guidelines.
Forums RSS Feed
Back to Forum List
|
Back to SalesLogix .NET Extensions
|
New Thread
View:
Dynamic
Flat
Tree
Search:
Author
Thread: .Net Extension design question using a webservice
David Nunnally
Posts: 206
.Net Extension design question using a webservice
Posted: 21 Sep 10 4:40 PM
I have a webservice I need to access inside of SLX 7.5.2. After much research it looks as though the preferred approach is to use a .Net Extension to handle the webservice. My service has 8 methods I need to access.
Question 1. I see from the examples that Run() is where the code is placed. Am I correct in assuming I will have to create 8 extensions. One for each method of my webservice? Or can a single extension be used.
Question 2. Most of the webservice methods return a single string value. However one returns an xml (array) of values for a dropdown control that I will need to populate a combobox with in my SLX form. How do I populate a SLX combobox from the extension that is getting an xml array from the webservice?
Thanks,
[
Reply
][
Quote
]
David Nunnally
Posts: 206
Re: .Net Extension design question using a webservice
Posted: 22 Sep 10 11:19 AM
After more research I came across Ryan's Embedding a .NET Control Screencast using an embedding .NET control. I believe I could eliminate my problems using this approach. In simplest terms I have a ro text box on the Opp tab with a button next to it. If the user clicks the button I pass the value of the text box to the embedded control. Let the user do all the work that requires the webservices and when they click Save it plugs the string result into the the text box. The .Net control would remove all of my issues in the previous post. However I am unclear about one thing in Ryan's sample readme.
Note, these samples were intentionally built to work in SalesLogix
version 6 and higher. They do not make use of .NET Extensions in
version 7. This means that you need to install and register the
.NET assemblies on each machine that will use them. Converting
these samples to .NET Extensions for v7 would remove the need
to distribute the samples to each workstation.
How to convert the sample to .Net Extension for v7.x?
Thanks,
[
Reply
][
Quote
]
Mark Dykun
Posts: 297
Re: .Net Extension design question using a webservice
Posted: 23 Sep 10 6:23 AM
David, your all of your methods could be off a single instance. Its possible to return an object that exposes all of your methods to call. I also suspect that you will not be returning XML nodes themselfs but the InnerText or attribute values as an string array { string[] } which you can iterate through and set your combobox from.
Kindest,
Mark
[
Reply
][
Quote
]
Page 1 of 1
You can subscribe to receive a daily forum digest in your
user profile
. View the site
code of conduct
for posting guidelines.
Forum RSS Feed
-
Subscribe to the forum RSS feed to keep on top of the latest forum activity!
slxdeveloper.com is brought to you courtesy of
Ryan Farley
&
Customer FX Corporation
.
This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.
code of conduct
|
page cache (param): 11/22/2024 9:46:03 AM