Webservices
Web Services for Achieve Beyond employees Please click on the appropriate service. Achieve Beyond Website; Employee Self Services; Email; Tracker; IT Helpdesk FAQ; Staff Training; Remote Support. For issues with any of the above services, please email us at it@achievebeyondusa.com. We will try to get back to you at our earliest convenience. Without Web Services, the HP server cannot communicate with the printer to monitor ink levels. HP Instant Ink cannot send new ink cartridges, and the printer might stop printing. If you enrolled in the HP Instant Ink service, you need to cancel your HP Instant Ink service separately. Returning Students: Register online through Web Services. Students on academic probation should report to the Office of Student Development & Counseling for advisement. New Students, Transfer, Readmitted, and Visiting Students will receive information about Advisement and Registration with acceptance letter package. Academic Advisement.
Web services are a lightweight, industry-standard way to make application functionality available to a variety of external systems and users. Microsoft Dynamics NAV 2018 supports creation and publishing of Dynamics NAV functionality as web services. You can expose pages, codeunits, or queries as web services, and even enhance a page web service by using an extension codeunit. When you publish Dynamics NAV objects as web services, they are immediately available on the network.
Developers can publish two types of web services from Dynamics NAV objects:
SOAP Web Services. You can publish either Dynamics NAV pages or codeunits as SOAP services.
OData Web Services. You can publish either pages or queries as OData services.
Dynamics NAV web services are stateless and do not preserve the values of global variables or single-instance codeunits between calls.
Web Service Protocols
The following table shows the types of web service applications that you can create for the web service protocols supported in Microsoft Dynamics NAV 2018.
| SOAP web services | OData web services | |
|---|---|---|
| Pages | Yes: Create, Read, Update, and Delete operations (CRUD) | Yes: Create, Read, Update, and Delete operations (CRUD) |
| Codeunits | Yes | No |
| Queries | No | Yes: Read-only |
For more information about the difference between these protocols, see Web Service Alternatives: SOAP and OData.
Page Web Services
When you expose a page as an OData web service, you can query that data to return a service metadata (EDMX) document, an AtomPub document, or a JavaScript Object Notation (JSON) document. You can also write back to the database if the exposed page is writable. For more information, see OData Web Services.
When you expose a page as a SOAP web service, you expose a default set of operations that you can use to manage common operations such as Create, Read, Update, and Delete. Page-based web services offer built-in optimistic concurrency management. Each operation call in a page-based web service is managed as a single transaction.
For SOAP services, you can also use extension codeunits to extend the default set of operations that are available on a page. Adding an extension codeunit to a page is useful if you want to perform operations other than the standard Create, Read, Update, and Delete operations. The benefit of adding an extension codeunit to a page is that you can make the web service complete by adding operations that are logical to that service. Those operations can use the same object identification principle as the basic page operations. For an example of how to implement an extension codeunit, see Walkthrough: Creating a Web Service using Extension Codeunits (SOAP).
Codeunit Web Services
For SOAP services only, codeunit web services provide you with the most control and flexibility. When a codeunit is exposed as a web service, all functions defined in the codeunit are exposed as operations.
Query Web Services
When you expose a Dynamics NAV query as an OData web service, you can query that data to return a service metadata (EDMX) document or an AtomPub document. For more information about how to create and use Dynamics NAV queries, see Queries.
Web Services and Regional Settings
Data is formatted according to the value of the Services Language setting for the relevant Microsoft Dynamics NAV Server instance. The default value is en-us. This means that Microsoft Dynamics NAV Server interprets all incoming data as the specified culture, such as dates and amounts.
If you know that the Services Language setting is always en-us, for example, your code can be based on that assumption. In a multilanguage environment, you will see more predictable transformations of data if data that is transmitted through web services is in a consistent culture.
Similarly, you can use the ServicesOptionFormat setting to specify how Microsoft Dynamics NAV Server must understand option values. If you set the ServicesOptionFormat setting to OptionString, Microsoft Dynamics NAV Server understand option values as the name of the option value, which is always en-us. If you set the setting to OptionCaption, web service data will be interpreted in the language specified by the Services Language setting.
Note
In earlier versions of Dynamics NAV, you could enable ServicesCultureDefaultUserPersonalization on the Microsoft Dynamics NAV Server instance. This was deprecated in Microsoft Dynamics NAV 2016 in order to guarantee that web services have a consistent culture.
Web Services in Multitenant Deployments
If your Dynamics NAV solution is used in a multitenant deployment architecture, you must make sure that any code that generates or consumes a web service specifies the relevant tenant. Web services are set up in the application, but typically you want to consume company-specific and tenant-specific data.
If you use the GETURL function, the generated URL will automatically apply to the user’s tenant ID. For more information, see GETURL Function.
The URL for accessing a web service in a multitenant deployment must specify the tenant ID in one of two ways: As a query parameter, or as a host name. If you use host names for tenants, the host name must be specified as an alternative ID.
For example, the following URL consumes the Customer ODATA web service for a specific tenant:
For more information, see Multitenant Deployment Architecture.
See Also
How to: Publish a Web Service
Web Service Alternatives: SOAP and OData
SOAP Web Service URIs
How to: Use SystemService to Find Companies
Basic Page Operations
Web Services Best Practices
Configuring Microsoft Dynamics NAV Server
Login to HCCWeb Services
Terms of Usage
You are entering a restricted information area. Any information you enter or change will be effective immediately unless otherwise noted, and you are responsible for such entries.
Please do not share your ID or password. If you believe someone else may know your password, change it at once. Anyone who shares his or her password is responsible for any transactions, whether willful or accidental, entered into the system.
The comments you enter in narrative sections fall within the institution's 'education record' and are subject to the guidelines created to protect the privacy of students. For more information on these guidelines, refer to the HCC Family Educational Rights and Privacy Act (FERPA) policy, or contact the Registrar.
I understand by my sign-on (username and Password) and by clicking the 'I Accept' button, I accept full responsibility for complying with the following:
Webservices.sos.state.tx
- I have access to view and comment on students. These records contain individually identifiable information. Student records are strictly confidential, protected under Federal law known as the (FERPA).
- I may access this information only in the legitimate educational interest of a student.
- Disclosure of this information to any unauthorized person could subject me to criminal and civil penalties imposed by law and could be cause for disciplinary action including termination of my employment.
The page you are trying to access requires authentication. Please enter your username and password to continue.