Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Primary ID vs Alternate ID populated in the log
I did a little searching to see if this question has been asked before and didn't find any specific solution.
I notice (take for example the Messier objects) the primary ID within the DB for most of these objects is the "MX" designator.
But for some of them the "MX" designator is populated in the Alternate ID field rather than the Primary ID field.

The system appears to auto-populate the Primary ID into the log entry.
And there doesn't appear to be any option for the user to edit that value.
So for example "KeyStone Cluster" is auto-populated in the log - where I would want "M13" - or "M13 Keystone Cluster"

For a given object - is there any way I can swap the Primary ID value with the Alternate ID value within the underlying DB?

Messages In This Thread
Primary ID vs Alternate ID populated in the log - by dw_Skyhound - 2019-09-06, 02:11 PM

Forum Jump:

Users browsing this thread: 1 Guest(s)