I am trying to change the where condition in my virtual table using the HTTP API. I can successfully create a virutal table, but if I try to update one I get an error that that table already exists. I am using the update command.
Does anyone know if it is possible to update a virtual table using the HTTP API to change the where condition in version 8.5 of Information Analyzer?
My backup solution is to create a global variable that contains the value I want to use in the virutal table where condition. I can successfully update global variables with the HTTP API, but I don't know how to use them in the where condition. Does anyone know if a global variable can be used in the where condition of a virtual table? If so, can you tell me the format to use it?
Re: Virtual Table updates with HTTP API2013-02-19T18:21:39ZThis is the accepted answer. This is the accepted answer.Since I was unable to modify the where condition, I came up with a different way.
Step 1) Create a new virtual table. (this currently works through the HTTP API)
Step 2) Use HTTP API to modify the binding of the rule to bind to the new virtual table.
Step 3) Execute the rule using HTTP API.
Step 4) Get rules of run from HTTP API and send to person to work issue with email.
I just thought I would put my solution out there. It may help others later.
smithha 110000PAKN162 Posts
Re: Virtual Table updates with HTTP API2013-02-20T16:06:59ZThis is the accepted answer. This is the accepted answer.
- tells 120000987Y
I am able to successfully update a Virtual Table in the current (9.1) version using the -update -projectContent command in the CLI (equivalent to the POST http://ServerName:9080/InformationAnalyzer/update&projectContent command in the API).
As for Global Variables, they are specific to the data rules and are not currently available for use in the Virtual Tables.
It looks like you were able to identify an effective approach for your needs.
Re: Virtual Table updates with HTTP API2013-02-20T17:33:43ZThis is the accepted answer. This is the accepted answer.It looks like the issue to update virutal tables was addressed in this patch: