Clarity

Expand all | Collapse all

Question on XOGing views

MarkCrump4459879

MarkCrump4459879Apr 10, 2015 11:54 AM

Roberto Barra

Roberto BarraApr 10, 2015 11:59 AM

Anon Anon

Anon AnonApr 10, 2015 12:26 PM

  • 1.  Question on XOGing views

    Posted Mar 18, 2015 12:44 PM

    Hi there,

     

    I'm in the process of learning how to XOG the project object from our DEV environment to TEST, with the obvious goal or promoting to PROD.

     

    I have XOGed out the lookups and the project object and moved them into TEST just fine.

     

    On the last step, I XOGed out the views using this command:

     

      <ViewQuery>

        <Filter name="code" criteria="EQUALS">property</Filter>

    </ViewQuery>

      <ViewQuery>

        <Filter name="code" criteria="EQUALS">list</Filter>

    </ViewQuery>

     

    I got a 94mb file output. Is this normal? Do I need to filter it just on the project object?

     

    Forgive the newbie questions. XOGing is very new to me.



  • 2.  Re: Question on XOGing views

    Posted Mar 18, 2015 01:07 PM

    I think that might pull in all the property views (not just the project ones).

     

    --

     

    <Filter name="object_code" criteria="EQUALS">project</Filter>

     

    should get all the views for an object but I have experienced odd results with that (I also get the object / lookups etc)

     

    --

     

    <Filter name="code" criteria="EQUALS">VIEW NAME GOES HERE</Filter>

     

    will just get a single view though, as long as you know the view name.



  • 3.  Re: Question on XOGing views

    Posted Mar 18, 2015 02:31 PM

    The criteria in the initial post is likely to pull also all the list views. Kinda surprising you did not get OOM error and that your system did not crash XOGing out a file of that size..

     

    If you XOG out the project object and do not use any limitin arguments you do get all the bells and whistles and the kitchen sink.

    That is you do not get only the OOTB views but also the user configured versions.



  • 4.  Re: Question on XOGing views

    Posted Mar 18, 2015 02:36 PM

    Huh,

     

    When I XOG'd out the project, I did not get the view and subpages (or, they didn't show back up when I xog'd them in.

     

    This is how I exported the XOG. Should I have done different code?

     

    <?xml version="1.0" encoding="UTF-8"?>

    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

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

    <Header version="8.0" action="read" objectType="contentPack" externalSource="NIKU">

    <!-- the contentType is used to determine which filter goes where -->

    <args contentType="job_definition" name="order_by_1" value="code"/>

    <args contentType="menu" name="order_by_1" value="code"/>

    <args contentType="view" name="order_by_1" value="code"/>

    <args contentType="process" name="order_by_1" value="code"/>

    <args contentType="object" name="order_by_1" value="code"/>

    </Header>

    <ObjectQuery>

    <Filter name="object_code" criteria="EQUALS">project</Filter>

    </ObjectQuery>

    </NikuDataBus>

     

    Thank you for all your help.



  • 5.  Re: Question on XOGing views

    Posted Mar 18, 2015 02:37 PM

    ^ no that XOG/XML should have pulled out the views as well I would expect.  Odd.



  • 6.  Re: Question on XOGing views

    Posted Mar 18, 2015 02:40 PM

    One of the guys here seems to remember an issue around views coming in on 13.1

     

    Obviosly, xoging back in a 94mb view output file isn't going to work.



  • 7.  Re: Question on XOGing views

    Posted Mar 18, 2015 02:49 PM

    Some times views have an issue with xog specially around partitions.  if you have partitions, i recommend you pull them by object (as mentioned by Dave), and partition.  Your XML should look like this

    <?xml version="1.0" encoding="UTF-8"?>

    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd">

        <Header action="read" externalSource="NIKU" objectType="contentPack" version="8.0">

            <args contentType="job_definition" name="order_by_1" value="code"/>

            <args contentType="menu" name="order_by_1" value="code"/>

            <args contentType="view" name="order_by_1" value="code"/>

            <args contentType="process" name="order_by_1" value="code"/>

            <args contentType="object" name="order_by_1" value="code"/>

        </Header>

        <ViewQuery>

            <Filter criteria="EQUALS" name="code">property</Filter>

            <Filter criteria="EQUALS" name="object_code">actionitem</Filter>

            <Filter criteria="EQUALS" name="partition_code">xx</Filter>

        </ViewQuery>

        <ViewQuery>

            <Filter criteria="EQUALS" name="code">list</Filter>

            <Filter criteria="EQUALS" name="object_code">actionitem</Filter>

            <Filter criteria="EQUALS" name="partition_code">xx</Filter>

        </ViewQuery>

    </NikuDataBus>

     

    This is still going to bring back a huge XML file, but then i would trim it using XSLT which will get rid of all the noise.  Here is the XSLT that you need to trim all that unnecessary noise (note that this trims all language codes as well except for en)

     

     

    <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

         <xsl:output indent="yes" />

         <xsl:strip-space elements="*" />

    <!-- #################################################### -->

    <!-- GLOBAL REPLACE FOR ALL XML FILES -->

    <!-- XSLT Template developped by IT-ROI Solutions -->

    <!-- July 2013 Views -->

    <!-- -->

    <!-- -->

    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->

    <!-- Change XOG Version to 12 -->

    <!-- Remove last updated by in all tags -->

    <!-- Remove XOG Output -->

    <!-- Remove General Tag -->

    <!-- #################################################### -->

    <!-- copy all nodes and attributes -->

         <xsl:template match="*|@*">

              <xsl:copy>

                   <xsl:apply-templates select="node()|@*" />

              </xsl:copy>

         </xsl:template>

    <!-- Change the XOG Version to 12.0-->

      <xsl:template match="@version[parent::Header]">

      <xsl:attribute name="version">

      <xsl:text>12.0</xsl:text>

      </xsl:attribute>

      </xsl:template>

    <!-- Remove Last updated by from all sections-->

      <xsl:template match="@lastUpdatedBy" />

    <!-- remove all XOGOutput Tags -->

         <xsl:template match="XOGOutput" />

    <!-- remove General  Tags as they are not needed and can cause errors -->

         <xsl:template match="General" />

    <!-- #################################################### -->

    <!-- END GLOBAL REPLACE FOR ALL XML FILES -->

    <!-- #################################################### -->

     

     

    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->

    <!-- Custom VIEW Specific code below -->

    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> 

         <!-- remove xsi:noNamespaceSchemaLocation -->

         <xsl:template match="@*[parent::NikuDataBus]" />

         <!-- remove all Tags whose languageCode atribute is not en -->

         <xsl:template match="*[@languageCode!='en']" />

         <!-- remove all pages Tags -->

         <xsl:template match="pages" />

      <!-- remove allobjects Tags -->

         <xsl:template match="objects" />

      <!-- remove all objects Tags -->

         <xsl:template match="objects" />

         <!-- remove all portlets Tags -->

         <xsl:template match="portlets" />

         <!-- remove all jobDefinitions Tags -->

         <xsl:template match="jobDefinitions" />

         <!-- remove all queries Tags -->

         <xsl:template match="queries" />

         <!-- remove all objects Tags -->

         <xsl:template match="objects" />

         <!-- remove all lookups Tags -->

         <xsl:template match="lookups" />

         <!-- remove all partitionModels Tags -->

         <xsl:template match="partitionModels" />

    </xsl:stylesheet>

     

    This should bring your xml to something totally manageable.

    hope this helps.

    Federico



  • 8.  Re: Question on XOGing views

    Posted Mar 18, 2015 03:58 PM

    You could also try to limit the result file by using

    <args name="singleContentType" value="object" />

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

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



  • 9.  Re: Question on XOGing views

    Posted Mar 18, 2015 04:19 PM

    Do I replace my args section with this, or add them to it?

     

    Also, we are only using one partition (System)

     

    Is there a way to limit the results to only English?



  • 10.  Re: Question on XOGing views

    Posted Mar 18, 2015 05:12 PM

    You try the effect of the arguments by adding one at a time.

    Regarding the languages with the current status of things you always read them out.

    However, then you clean the output file with Federico's XLTS scripts.



  • 11.  Re: Question on XOGing views

    Posted Mar 18, 2015 05:15 PM


  • 12.  Re: Question on XOGing views

    Posted Mar 19, 2015 11:46 AM

    Ok, an update

     

    I did some digging around and I have verified that the information I'm missing is showing up in the view export. That's the good news.

     

    Using urmas's args I created the following XML read file:

    <?xml version="1.0" encoding="UTF-8"?>

    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd">

      <Header version="8.0" action="read" objectType="contentPack" externalSource="NIKU">

        <!-- the contentType is used to determine which filter goes where -->

    <args name="singleContentType" value="object" />

    <args contentType="job_definition" name="order_by_1" value="code"/>

    <args contentType="menu" name="order_by_1" value="code"/>

    <args contentType="view" name="order_by_1" value="code"/>

    <args contentType="process" name="order_by_1" value="code"/>

    <args contentType="object" name="order_by_1" value="code"/>

      </Header>

     

      <ViewQuery>

        <Filter name="code" criteria="EQUALS">property</Filter>

      </ViewQuery>

      <ViewQuery>

        <Filter name="code" criteria="EQUALS">list</Filter>

      </ViewQuery>

     

    </NikuDataBus>

     

    That created a much more manageable xml file (about 2mb). Unfortunately when I try and XOG that file into the test environment, I get the following error in the output file:

    <XOGOutput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/status.xsd">

      <Object type="contentPack"/>

      <Status elapsedTime="0.001 seconds" state="FAILURE"/>

      <Statistics failureRecords="0" insertedRecords="0" totalNumberOfRecords="0" updatedRecords="0"/>

      <ErrorInformation>

        <Severity>FATAL</Severity>

        <Description>[Error] :0:0: tag name "links" is not allowed. Possible tag names are: &lt;nls&gt;

    [Error] :0:0: tag name "links" is not allowed. Possible tag names are: &lt;nls&gt;

     

    Grr. I am so close yet so far away.



  • 13.  Re: Question on XOGing views
    Best Answer

    Posted Mar 19, 2015 02:06 PM

    HI Mark,

    I would add the object code to your read file to limit to just your project object (such as below).  if you still get the error after adding that, feel free to send me the xml and i will build an XSLT to fix this issue.

    cheers,

    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd">

        <Header action="read" externalSource="NIKU" objectType="contentPack" version="8.0">

            <args contentType="job_definition" name="order_by_1" value="code"/>

            <args contentType="menu" name="order_by_1" value="code"/>

            <args contentType="view" name="order_by_1" value="code"/>

            <args contentType="process" name="order_by_1" value="code"/>

            <args contentType="object" name="order_by_1" value="code"/>

        </Header>

        <ViewQuery>

            <Filter criteria="EQUALS" name="code">property</Filter>

            <Filter criteria="EQUALS" name="object_code">project</Filter>

           

        </ViewQuery>

        <ViewQuery>

            <Filter criteria="EQUALS" name="code">list</Filter>

            <Filter criteria="EQUALS" name="object_code">project</Filter>

        

        </ViewQuery>

    </NikuDataBus>



  • 14.  Re: Question on XOGing views

    Posted Mar 19, 2015 02:35 PM

    I recall getting that error maybe in 12.0. If I recall correctly I manually moved those sections having the Link tag.

    Federico's scripts would do that with no effort at all.



  • 15.  Re: Question on XOGing views

    Posted Mar 19, 2015 03:38 PM

    Thank you all for your help. Federico helped me out with the XLST (something I need to do more research on).

     

    I generated an input file that *seems* to have posted the missing views. I'm waiting for the guy who built the views to come back to his desk and look.

     

    Thanks again everyone, I can't even begin to state how big a help you've been.



  • 16.  Re: Question on XOGing views

    Posted Mar 19, 2015 04:02 PM
      |   view attached

    for everyone's reference i attached the xslt that was used. 

    it basically removes all the noise, keeps the views tag only and removes language code.

     

    this will work with all views.

    Also Mark, if you ever need an XSLT file, let me know i probably have the logic that you need as we have a library that contains hundreds of them to clean up XOG.

    cheers,

    Federico

    Attachment(s)

    zip
    views.xslt.zip   913 B 1 version


  • 17.  Re: Question on XOGing views

    Posted Mar 19, 2015 04:08 PM

    Thanks!

     

    I've put XLST on my learn list for next week.

     

    For obvious reasons, I'm not thinking of this problem for 14 hours



  • 18.  Re: Question on XOGing views

    Posted Apr 10, 2015 11:06 AM

    So, it turns out something went wrong and when I try and bring up the View tab in the Object, I get a message to contact my system admin. After talking with CA support, it looks like the list view didn't come in properly. We walked through xogging out just the list view. When I went to xog it back in, I got the following error on my output file:

     

    <XOGOutput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/status.xsd">

      <Object type="contentPack"/>

      <Status elapsedTime="0.001 seconds" state="FAILURE"/>

      <Statistics failureRecords="0" insertedRecords="0" totalNumberOfRecords="0" updatedRecords="0"/>

      <ErrorInformation>

        <Severity>FATAL</Severity>

        <Description>[Error] :0:0: tag name "list" is not allowed. Possible tag names are: &lt;Documents&gt;,&lt;Forms&gt;,&lt;Processes&gt;,&lt;jobDefinitions&gt;,&lt;lookups&gt;,&lt;menus&gt;,&lt;objectMappings&gt;,&lt;objects&gt;,&lt;pages&gt;,&lt;partitionModels&gt;,&lt;portlets&gt;,&lt;queries&gt;,&lt;views&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "indicatorImage" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "indicatorImage" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "tsv" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "gantt" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "indicatorImage" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "gantt" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "tsv" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "indicatorImage" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "tsv" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "indicatorImage" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "indicatorImage" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "tsv" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "indicatorImage" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "gantt" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "indicatorImage" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "gantt" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "indicatorImage" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "tsv" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: uncompleted content model. expecting: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "tsv" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "column" is not allowed. Possible tag names are: &lt;nls&gt;,&lt;section&gt;

    [Error] :0:0: tag name "tsv" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "tsv" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "tsv" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "tsv" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    [Error] :0:0: tag name "gantt" is not allowed. Possible tag names are: &lt;OBSAssocs&gt;,&lt;Security&gt;,&lt;action&gt;,&lt;aggregationRow&gt;,&lt;column&gt;,&lt;columnDimension&gt;,&lt;filter&gt;,&lt;metricColumn&gt;,&lt;nls&gt;,&lt;uomConversion&gt;

    </Description>

        <Exception type="java.lang.Exception">Invalid xml data</Exception>

      </ErrorInformation>

    </XOGOutput>



  • 19.  Re: Question on XOGing views

    Posted Apr 10, 2015 11:37 AM

    "tag name "list" is not allowed. Possible tag names are..."

     

    Sounds like you are missing a "level" in the XML structure, <list> is a valid tag but it needs to be within the right tag structure (no-idea if any of that is the correct terminology for XML!)

     

    Structure should be something like...

     

    <NikuDataBus>

        <Header/>

        <contentPack>

            <views>

               <list>

            </views>

        </contentPack>

    </NikuDataBus>



  • 20.  Re: Question on XOGing views

    Posted Apr 10, 2015 11:41 AM

    Ah, this makes sense.

     

    This is the top of my input file. It sounds like I need to add the Content Pack, Views, and List tag structures and close them.

     

    ikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_contentPack.xsd">

      <Header action="write" externalSource="NIKU" objectType="contentPack" version="13.1.0.0248"/>

      <contentPack update="true">

    <list allowConfigure="true" allowConfigureLabel="true" allowEditing="false" code="itl.associatedIssuesList" dataProviderId="associatedIssuesList" dataProviderPartitionId="NIKU.ROOT" dataProviderType="system" defaultSortColumn="name" defaultSortOrder="ascending" forceFilter="false" gridAttributeProtection="1" hasEditableColumn="false" metricsLocation="bottom" showAltValueText="false" showColumnCurrencyCode="false">

      <nls languageCode="zh" name="Associated Issues List"/>

    (and more stuff)



  • 21.  Re: Question on XOGing views

    Posted Apr 10, 2015 11:52 AM

    Yeah, from that fragment it looks like you are just missing the <views> tag.



  • 22.  Re: Question on XOGing views

    Posted Apr 10, 2015 11:56 AM

    In that snippet, you are missing only <views> tag!

     

    Does your XOG contains <property> view tag too? If so, they must come before <list> tags.



  • 23.  Re: Question on XOGing views

    Posted Apr 10, 2015 11:48 AM

    Can you attach the XOG file that you are trying to XOGin?



  • 24.  Re: Question on XOGing views

    Posted Apr 10, 2015 11:54 AM
      |   view attached

    Sure:

    Attachment(s)

    zip
    HIT_listvw_write.xml.zip   108 KB 1 version


  • 25.  Re: Question on XOGing views

    Posted Apr 10, 2015 11:59 AM

    tks, only add the views tag and try again!



  • 26.  Re: Question on XOGing views

    Posted Apr 10, 2015 12:35 PM

    Hi Mark,

    did you get this error on the object that you xogged in the original thread? or is this a new object? or new XOG.



  • 27.  Re: Question on XOGing views

    Posted Apr 10, 2015 12:38 PM

    Both

     

    When I XOGed in the file I got from you, after the fact I noticed I couldn't bring up the views in the project object.


    CA support walked me through XOGing out the list view and that's what I'm trying to XOG back in.



  • 28.  Re: Question on XOGing views

    Posted Apr 10, 2015 12:48 PM

    I am having a hard time understanding what happened, but lets see if we can help you out.

    First, when you xogged the views (from the XML file on March 19), you were able to see the view changes in the application side of clarity?

    When you xogged in that file, you started seeing issues on the admin side>Objects>projectObject>views tab?  This is where you got the system 500 error?  If this is correct, can you repeat that navigation, then go to the app log, and send me the snippet from the log that you get during that time frame?

    I think it could be a deeper issue than just trying to push in the list view for that object.

    Views are somewhat finicky with XOG, and it is important to know where the error is that is giving you the contact system admin.



  • 29.  Re: Question on XOGing views

    Posted Apr 10, 2015 12:51 PM
      |   view attached

    Sure,

     

    here is the log file I sent CA.

    Attachment(s)

    zip
    app-ca.log.zip   138 KB 1 version


  • 30.  Re: Question on XOGing views

    Posted Apr 10, 2015 01:00 PM

    Can you make sure these two lookups exist in your target environment 

    OBS_BROWSE_FLT_MODE_PRJ

    OBS_BROWSE_FLT_MODE_RES

    Something in the view is referencing them and it appears that they do not exist.



  • 31.  Re: Question on XOGing views

    Posted Apr 10, 2015 01:08 PM

    They do not!

     

    Can I just create a dummy lookup with those name?



  • 32.  Re: Question on XOGing views

    Posted Apr 10, 2015 01:14 PM

    I would xog them in from the source environment.

    I have a feeling that is the source of your problem.  The other question is, and this is the million dollar question (which i think is the cause of the whole problem), when they created the new views (i am guessing they also created attributes), did you XOG in the attributes before the views?   My guess is, that if you are missing the lookups, you are problably missing the attributes, and this is what is causing all your issues.

     

    So first thing, is to find out which attributes in your source system you are missing, then move those attributes (make sure you move the lookups that are associated with those attributes first).

    Then xog in the file with the views from mid march, and your problems should be over.

    if you want, i can walk you through it.

    Cheers,

    Federico



  • 33.  Re: Question on XOGing views

    Posted Apr 10, 2015 01:20 PM

    I don't think I did any of the attributes.

     

    I XOGed out the new lookups, then the project object, then the idea object, and then your view object.



  • 34.  Re: Question on XOGing views

    Posted Apr 10, 2015 01:23 PM

    Hold on: I had to search by name, those Lookups are in the final environment.



  • 35.  Re: Question on XOGing views

    Posted Apr 10, 2015 01:25 PM

    well the attributes are in the project object read (theoretically).

    can you run this query in the source and target system, then send me the results. this will tell me if my theory is correct. the results should match

     

    select internal_name,

      data_type,

      Extended_type,

      data_size,

      lookup_type,

      Object_name,

      partition_code,

      is_active

    from odf_custom_attributes

    where column_name <> 'partition_code'

    and object_name IN('project','idea')

    --and partition_code='NIKU.ROOT'

    --and is_active=1

    order by object_name



  • 36.  Re: Question on XOGing views

    Posted Apr 10, 2015 01:29 PM

    Do I just copy and past that into the the NSQL section when I create a new Query?



  • 37.  Re: Question on XOGing views

    Posted Apr 10, 2015 04:22 PM

    Federico helped me solve the problem, and wins Forum Helper of the century award.



  • 38.  Re: Question on XOGing views

    Posted Apr 10, 2015 12:20 PM
      |   view attached

    It's complaining about the view tag, now.

     

    Did I put it in the wrong place?

     

    Sorry about this. XML editing is outside of my wheelhouse.

    Attachment(s)

    zip
    HIT_listvw_write.xml.zip   108 KB 1 version


  • 39.  Re: Question on XOGing views

    Posted Apr 10, 2015 12:26 PM

    its <views> not <view>



  • 40.  Re: Question on XOGing views

    Posted Apr 10, 2015 12:29 PM

    That would do it.... :./

     

    Now I'm getting: [Error] :0:0: unexpected attribute "thresholdAggregationTypeCode"

     

    Can I delete that section?



  • 41.  Re: Question on XOGing views

    Posted Apr 10, 2015 12:57 PM

    I never had problem with this before...

     

    XOG is complaining about a column in a list view that is formatted as a Gantt.

     

    Are you trying to XOG between different versions of Clarity?

     

    As a test, you can try to remove the tag aggregationBar from the XML and XOG again (don't try it on production, please!! ).

     

    This tag do not seems to be required (at least, not by the xsd). If it works, you will need to reconfigure this column on Clarity.



  • 42.  Re: Question on XOGing views

    Posted Apr 10, 2015 12:59 PM

    If the error persist, try to remove the tag bar too. (same warnings apply!)