The problem is due to a known limitation. We allow for only a single WsQuery nested class to be created within an Entity class, so the first checked method will be the only method created. The use of only a single nested WsQuery per Entity was intentional, and follows our implementation of stored procedure backed entities. The good news is that these nested classes are really just helper classes defined to make constructing a WsQuery easier, and are not required to be used.
There are a couple workarounds to look at:
1) Since the *DataRow classes are partial, you can write your own additional WsQueryX nested class, using the existing class as a template so that you only need to change the parameter and execute information. You donít need to make the class nested if you prefer not to, since the nesting is just a convenience not a requirement.
2) Call the base IdeaBlade.Persistence.WS.WsQuery class directly. Here again you can consult an existing nested class to see how it constructs the base WsQuery. Getting the constructor right is the primary difficulty here. Youíll want to use either:
public WsQuery(String pServiceName, String pMethodName, Type pEntityType, WsProxyType pProxyType) or
public WsQuery(Type pClientProxyType, String pMethodName, Type pEntityType) - preferred