This post is our own opinion and does not necessarily reflect the opinion or view of our companies or Microsoft.
When I try to install Web Services on IIS for Retails POS Component, and I got the problem.
This scenario shouldn’t be common in a production environment, but, it is indeed quite common in a VM machine (I’m using virtual machine Hyper-V on Windows 8.1)
Form interaction classes that allow user interface control logic to be shared across forms. For instance, controlling which buttons are available to a list page and the associated detail form.
The interaction classes are extending a base ListPageInteraction class. This has some methods supported by the kernel to interact e.g. with initializations of the list page form. Other classes can be build stand alone to execute e.g. a batch process or represent a web service or posting classes.
Form interaction classes are not mandatory for list pages but should be used on data entry forms that require logic. This ensures consistency and allows easier maintenance of logic.
This class inherits
from SysListPageInteractionBase, here is some methods we need to know
initializing: Called when the form is initializing – Similar to the form init method
intializeQuery: Also called when the form is initializing – Similar to the datasource init method.
selectionChanged: Called when the active record changes – Similar to the datasource active method.
setButtonEnabled: Should be overridden to dynamically enable/disable buttons based on the current selection. This is called from the selectionChanged method.