Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies replies
    2
  • Answers answer
    1
  • Subscribers subscribers
    13
  • Views views
    195
  • Users 0 members are here
Related
Options

XML Generator file location for PPM 10.0.4

Kaushik Datta

Hi,

Can i get the path to download the ITGXMLGenerator for importing requests in PPM 10.0.4? We are having the 9.3 version, and not sure if it is working correctly or not.

Thanks,

Kaushik

  • Suggested Answer

    0  

    Hi Kaushik,

    We're still using that old faithful 9.3 version for our own usage today on PPM 24.3, so the version you're having is still working fine. However, please be aware that the PPM XML Importer is only supposed to be used as part of a Professional Service Engagement (officially). 

    What entities are you using it to import into PPM, and what PPM version are you currently on? I'm just asking in case there's a different better (and supported) way to import entities into PPM.

  • 0 in reply to    
    Hi guys,

    I was able to download and use the 'PPM_XML_Importer_9.3'. I successfully imported a project
    with typical fields; however, I have fields that are of the 'Autocomplete List' type and are 
    dependent on other fields, and I am unable to import them. 
    Could you guide me on how to populate these values?

    Currently, I receive the following error:

    Import Identifier: 1729117957207
    Import Started: 16 de octubre de 2024 19:32:37 CLST
    Test Mode - no records will be created in ITG.
    Abort process after 10 failures.
     
    Project identified by "Testing of XML Project1"
    Error 2: Fail to apply value 'Territorial' for field REQ.SGP_TIPO. If it is validation error, check the validation definition to make sure all TOKENs it depends on can be resolved. Detail error: Uno de los tokens de la validación no se pudo analizar. Esto puede deberse a que un nombre de token no es válido o a que faltan datos en el campo que representa el token. (KNTA-10073).
    Error 2: Error validating field REQ.SGP_SUBINSTRUMENTO: contains multiple values, but field does not support multiple values.
    Error 2: Fail to apply value 'Individual' for field REQ.SGP_SUB_TIPO. If it is validation error, check the validation definition to make sure all TOKENs it depends on can be resolved. Detail error: Uno de los tokens de la validación no se pudo analizar. Esto puede deberse a que un nombre de token no es válido o a que faltan datos en el campo que representa el token. (KNTA-10073).
    Error 2: Fail to apply value 'Implementación' for field REQ.SGP_FASE_INST. If it is validation error, check the validation definition to make sure all TOKENs it depends on can be resolved. Detail error: Uno de los tokens de la validación no se pudo analizar. Esto puede deberse a que un nombre de token no es válido o a que faltan datos en el campo que representa el token. (KNTA-10073).


    Import Finished: 16 de octubre de 2024 19:32:37 CLST
    Import Completed with Errors.
    The result is:
        # passed: 0.
        # failed: 1.
        # skipped: 0.
    Excel:
    *Field Prompt: Project Name: (OK) Project Type (OK) Project Managers: (OK) Planned Start: (OK) Planned End: (OK) Region (OK) Short Desc (OK) Status (OK) Creation Date (OK) Código: (OK) Instrumento: (OK) Fase instrumento: (error) field Lista autocompletar Subinstrumento: (error) Tipo: (error) Subtipo: (error)
    Identifier Project Name Project Type Project Managers Planned Start Planned End Region REQ.DESCRIPTION REQ.STATUS_ID REQ.CREATION_DATE REQ.SGP_CODIGO REQ.SGP_INST REQ.SGP_FASE_INST REQ.SGP_SUBINSTRUMENTO REQ.SGP_TIPO REQ.SGP_SUB_TIPO
    1 Testing of XML Project1 Proyecto General Admin User 01-01-2024 01-12-2025 CHILE Description Testing of XML Project1 Adjudicación 01-01-2024 PR_01_0001_PI_0001 ENCCRV Implementación FERI Territorial Individual

    Regards,

    Pedro

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.