Book a Demo

Author Topic: createBaseLine returns false  (Read 3966 times)

Oliver F.

  • EA User
  • **
  • Posts: 573
  • Karma: +2/-1
  • Aren´t we all in the model business ?
    • View Profile
    • Karl Storz homepage
createBaseLine returns false
« on: September 26, 2008, 11:34:26 pm »
I wondered what might be the criteria for Repository.createBaseline to return false as result.

What I have checked so far:

- The package is unlocked (apply user lock) by the correct user
- The correct XMLGUID is used to define the package in question
- Version and notes are unique
- It works manually from within EA with the same user and package
- The same result from EAP file and SQL server repository

Unfortunately the method is not very descriptive when it comes to errors and the manual is not very helpful here either.

Oliver

Oliver F.

  • EA User
  • **
  • Posts: 573
  • Karma: +2/-1
  • Aren´t we all in the model business ?
    • View Profile
    • Karl Storz homepage
Re: createBaseLine returns false
« Reply #1 on: September 30, 2008, 05:01:23 pm »
Thanks to Sparx here is the answer:

============
Hi Oliver,

Thanks for your email regarding createBaseline not working. We
identified this issue earlier on in this development cycle and have
found that the behaviour of the baseline methods are unfortunatley
inconsistent with the documentation.

- The documentation states that DoBaselineCompare, DoBaselineMerge,
GetBaselines and CreateBaseline should accept an XML formatted package
GUID
- Currently the methods actually accept only non formatted guids

[...]

===========

Oliver

mrf

  • EA User
  • **
  • Posts: 311
  • Karma: +0/-0
    • View Profile
Re: createBaseLine returns false
« Reply #2 on: September 30, 2008, 05:05:42 pm »
This issue should be resolved in the next release of EA making it consistent with the API documentation. For backwards compatibility the four methods mentioned will accept both XML and non-XML formatted GUIDS.
Best Regards,

Michael

[email protected]
"It is more complicated than you think." - RFC 1925, Section 2.8