edit the GUID

[alemanda]

Hi to all,
is it possible in someway overwrite the GUID?

[Laszlo Nagy]

I believe the GUID is automatically assigned to library pats by ArchiCAD when they are created.
So I think it is not possible.

I don't know if it is possible using API or not.

[Jochen Suehlo]

I changed the GUID of a new object to the number of an excisting object, that the new one should have, so it will be recognized.
This was not possible in ArchiCAD; first I converted both objects into XML files with the XML Converter, than I changed the GUID within the XML file, then converted the new object back to gsm.

[alemanda]

XML converter? Where can I find it?
How does it wokrs?
Anyway this is a very good new!!!

[Jochen Suehlo]

XML Converter is a bit tricky to use, because it is a command line tool.
AC 14 has it within its directory. FOR AC 13 you have to download the Library Developer Toolkit at:
http://www.graphisoft.com/support/developer/downloads/

For use of the Converter take a serach in this forum "XML Converter"

[Barry Kelly]

Doing a "Save As" and giving the object a new name will change the GUID I believe.
But you have no control over what it is.
Barry.

[ztaskai]

As Barry told, you get a brand new MainID if you save the object to a new location via 'save as'. On the other hand, you can claim the MainID of an other object by overwriting it in 'save as'.

This method works in v14 but I'm not sure about v13.

Regs,

[Karl Ottenstein]

ztaskai wrote:
As Barry told, you get a brand new MainID if you save the object to a new location via 'save as'. On the other hand, you can claim the MainID of an other object by overwriting it in 'save as'.

This method works in v14 but I'm not sure about v13.

Regs,

Thanks for this, Barry and Zsolt. But, what a pain...

I'm helping someone transition from 9 to 14 right now, and their old custom library parts reported as duplicated in the 14 lib manager. On looking, the root GUID was identical for non-identical parts. I wasted some time doing Save As with each part, one by one, back to the same name - only to find no improvement.

How frustrating that you have to do a Save As to a NEW name to get the base GUID to change ... and then delete the original part, and optionally rename the newly named part back to the desired name... and that this must be done one, by one.

Further frustrating that this migration process is not discussed anywhere in the AC 14 Help or Reference Guide, nor on the Wiki.

So, rambling with a few more keywords in this post in case someone else runs into this issue and does a forum search. 😉

Karl

[ztaskai]

Hi Karl,

Dropping explicit controls over the GUIDs was intentional. The design tries to emphesize the nature of libpart identification. I'm confident it is more intuitive for people less experienced with objects. It is a hassle for you, of course:(

I'd like to add one more thing for later finders of this thread (as it may be too late for you). If I had to give new GUID to more than 12 elements, I would convert them to XML using LP_XMLConverter. There you can make a mass-replace replacing the main part of the ID with the revision part (which just serves as a reliable new-GUID-source for the operation).

In Perl it goes like this:

binmode INFILE;
my $fileContent = <INFILE>;
close (INFILE);

if ($fileContent =~ /<Ancestry[^>]+Template="no"[^>]*>/) {
  @lines = split (/\n/, $fileContent);
  @lines = map {$_ = $_ . "\n"} @lines;
  $/ = $irs;

  if (!(open (OUTFILE, '>' , $origname))) {
    print $logFileHandle "Error: Unable to write $origname. Skipping.\n";
    return;
  }
  select(OUTFILE);
  binmode OUTFILE;
  foreach $_ (@lines) {
    if (m/<Symbol([^>]+)UNID="\{[^\}]+\}-([^\"]+)"(.*)/i) {
      print "<Symbol$1UNID=\"$2-$2\"$3\n";
    } else {
      print ("$_");
    }
  }
  close(OUTFILE);
  select (STDOUT);
  print ".$origname...\n";
}

I also attached a full Perl script changin the IDs of a folder of XML fomat library parts.

HTH,