Expand all | Collapse all

[XOG] Use a read XOG and only get specific Custom Information

Jump to Best Answer
  • 1.  [XOG] Use a read XOG and only get specific Custom Information

    Posted 12-02-2014 04:50 PM

    I am wondering if it is possible to use a Read XOG and only read specific custom information.  I know I can turn "include_custom" on or off based on the XOG below:



        xmlns:xsi="" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd">

        <Header action="read" externalSource="NIKU"

            objectType="project" version="6.0.11">

            <!-- you change the order by simply swap 1 and 2 number in the name attribute -->

            <args name="order_by_1" value="name"/>

            <args name="order_by_2" value="projectID"/>

            <args name="include_tasks" value="true"/>

            <args name="include_dependencies" value="true"/>

            <args name="include_subprojects" value="true"/>

            <args name="include_resources" value="true"/>

            <args name="include_baselines" value="true"/>

            <args name="include_allocations" value="true"/>

            <args name="include_estimates" value="true"/>

            <args name="include_actuals" value="true"/>

           <args name="include_custom" value="true"/>



            <Filter criteria="EQUALS" name="projectID">ACT00000458</Filter>




    Obviously if I make the value "true" it will return all custom subobjects and attributes.  Likewise, if I make the value "false" it will only return the OOTB values.  I know I can do this by doing a full read XOG and then using a style sheet or gel parsing, but I am looking for a less memory intensive way.  Is there any way to only read/not read specific custom information in the XOG? (i.e. one custom subobject and not the other)

  • 2.  Re: [XOG] Use a read XOG and only get specific Custom Information
    Best Answer

    Posted 12-02-2014 05:02 PM

    Don't think "XOG" can do that, but you can call a custom-query (which could just returns the fields that you care about) over the query-api in much the same way as you call XOG.

    Since the query is custom defined, this is really flexible.


    See here for a walkthru;

    Obtaining NSQL Query Output via XOG :