Discussions

The question I have today is why would the iMIS documentation at: https://developer.imis.com/docs/using-the-client-library-asisoaclientservices give explicit examples and instruction on how to access the ASI Client Services?

More specifically the IoC Support error crops up from the below code:

Code DIRECTLY pulled from your own documentation, so is it common practice for your documentation to have non functional code?

I can see a lot of advantages to the REST API and have begun implementing it where I can, but for obvious reasons (at least again based on documentation) this API is not a “solve all” when compared to pre-existing functionality….

The above code is an example of dynamic data access to iMIS accessing BOD tables/views… This has been a very convenient way for us to access data in the past and again, based on current documentation should still very much be a viable option for .NET developers to avoid hundreds of rest call from the back end where a single dynamic typed method can query the imis data at large

Based on your recommendations am I to believe your documentation needs edits and I am to ignore the entire iMIS SDK section?

Is my alternative here really to take any method that uses the BOD’s for data access and import that BOD into an IQA, assign the list of parameters possible for an entire table/view to have and filter by, then to code around these IQAs in a rest call, and then at deploy time be sure to not only move up my code from our repository but RECREATE every IQA then in our production environment as well?

Am I the only one who sees this as a step backwards? Turning what used to be one easy to use method into hundreds of explicit calls to IQAs and overhead of putting each column as a filterable parameter to be optional?

As the lead developer here my superiors rely on me to communicate ease of use and implementation to our systems, despite optimism that this major upgrade would go differently than those in the past it seems once again the support I receive is confusing and dismissive at best, unless I’m missing something the route being advocated doesn’t handle all that I need..

This is code that accesses to aforementioned dynamic method, it’s purpose is to simply retrieve an order and the lines related to it from a custom BOD we have created within imis, I understand that one way to solve this would be creating an IQA that references these BODs then accepts a parameter of ORDER_NUMBER, but this is one of hundreds that access imis in this fashion, and if I’m being told your documentation is incorrect in still touting this as a .NET capability within the iMIS SDK then this has caused a very inaccurate representation on my end for level of effort, and will be the direct cause of pushed deadlines…

Furthermore as you’ve stated it took an answer from your Director of Development to get clarity on the IoC Support error, a lot of what I’m dealing with currently is deeper than I feel a simply discuss post would remedy, with as much as we pay for support a dismissive push to a community forum does not feel like the appropriate response to pleas for help from a client who is held at a standstill due to potential inaccuracies in documentation and restrictive support measures, it is my opinion that support should be offered in real-time for a case as intricate as this, that said the future of our business with iMIS can be made our broken by the implementation of EMS, for which currently is not going well…