Tagged with xml - Visokio Forums http://forums.visokio.com/discussions/tagged/xml/feed.rss Mon, 30 Oct 17 12:25:15 -0400 Tagged with xml - Visokio Forums en-CA Data sources: Saving XML Custom Mapping 'Template'?? http://forums.visokio.com/discussion/3247/data-sources-saving-xml-custom-mapping-templatess Fri, 02 Jun 2017 05:51:35 -0400 Jamie_Lambert 3247@/discussions

Every day we run this API and some days map fine, but other days Omniscope struggles to correctly parse the results and omits columns of data that we need. I think this is probably because the URL query changes slightly each day- it’s not one, set URL because part of the URL changes with a daily “job ID” code. The data / response is in the exact same layout day to day. We’ve experimented with unticking the auto-recognise options under Parsing and haven’t yet found a combination that consistently works across different daily queries.

We can go in and edit the custom mapping to re-tell Omniscope how to correctly lay out the data, but are hoping there’s a way to ‘save’ these settings to work across daily requests rather than having them erased each time a new URL is entered and having to manually tick the checkboxes for row, column etc. So, essentially, my question is; Can we save our custom mapping layout as a template to apply across URL queries which, although they technically change daily, are all consistent in layout?]]>
Filtering: Querying for all non-null values in xml? http://forums.visokio.com/discussion/2558/filtering-querying-for-all-non-null-values-in-xmls Wed, 14 May 2014 06:51:43 -0400 Bart 2558@/discussions
When building the query in omniscope, is there a way to exclude value rather than select all values.

Let's say we have a field with values : null,A,B,C,D,E,F

I am deselecting value null, so we have A,B,C,D,E,F left only. Next I am building the query based on filters so in xml I am getting :

cellvalue column="Field" summary="No summary available">
object value="A" type="String" />
object value="B" type="String" />
object value="C" type="String" />
object value="D" type="String" />
object value="E" type="String" />
object value="F" type="String" />
/cellvalue>
/selection>

Rather than having this I would like to state something like :
selection>
cellvalue column="Field" summary="No summary available">
object value!=null />
/cellvalue>
/selection>
but I am getting an error saying that value needs to have "=" sign and it can't have "!=".

For now I need to build a new query whenever new value comes in, otherwise it doesn't work as it is selecting values which were selected in xml previously.

Bart]]>
Idea: Scheduler watchfolder - process files in copied order? http://forums.visokio.com/discussion/2351/idea-scheduler-watchfolder-process-files-in-copied-orders Thu, 19 Sep 2013 05:06:00 -0400 alec_webliquid 2351@/discussions
Would it be possible to implement functionality to process scheduler XML files in the order that they are copied to the watch folder? I have my processes set up in a sequential, multi-file structure, similar to the way you advise for the .iok files themselves. I would love to be able to copy all my XML files to the watch folder at once and trust that they will be processed in the correct order. Currently, I have to do it in two lots as there is no guarantee it will happen this way.

I am aware I could write more XML files which deal with all of my .iok files at once, and I may do so in the short term, but this is still something I would very much like to see if possible.

Is this request feasible?

Cheers]]>
Sources: Improved XML data import (2.8+) http://forums.visokio.com/discussion/1871/sources-improved-xml-data-import-2.8- Mon, 29 Oct 2012 06:15:39 -0400 richard 1871@/discussions
1. Add in an XML file using the 'Data file' source and choose 'Definition' as the transform type
2. Edit the definition and using the table, select the tags/attributes to import into the dataset.
3. Choose the tag/attribute ('Record item') which will identify dataset records in the XML data

Additional options include the default labelling format for the dataset fields and previews of the XML and dataset.]]>