_NGA_G internal dps don't match configured archive groups

[tpjctrl]

Stumbled upon this when importing some dps which reference _NGA_G_STATUS dps, but errored on import. After having a close look at it, it seems that for some reason the internal dps for archives didn't all get created when the archive groups were made (also some got created but afterwards the groups got renamed, yet the dps stayed with the old name).

Archive groups as seen in Archive Group Management (under Runtime Engineering):
ALERT
STATES
EVENT
MEAS_SUBSTATION
MEAS_WIND
EVENT_MS
MEAS_BATTERY
CONFIG
LOGBOOK

_NGA_G* dps in the database:
# Datapoint/DpId
DpName TypeName ID
_NGA_G_EVENT _NGA_Group 460
_NGA_G_EVENT_2 _NGA_Group 461
_NGA_G_ALERT _NGA_Group 462
_NGA_G_ALERT_2 _NGA_Group 463
_NGA_G_Group1 _NGA_Group 516
_NGA_G_Group1_2 _NGA_Group 517
_NGA_G_NZL_MEAS_SUBSTATION _NGA_Group 518
_NGA_G_NZL_MEAS_SUBSTATION_2 _NGA_Group 519
_NGA_G_MEAS_WIND _NGA_Group 524
_NGA_G_MEAS_WIND_2 _NGA_Group 525
_NGA_G_MEAS_BATTERY _NGA_Group 526
_NGA_G_MEAS_BATTERY_2 _NGA_Group 527
_NGA_G_CONFIG _NGA_Group 528
_NGA_G_CONFIG_2 _NGA_Group 529
_NGA_G_LOGBOOK _NGA_Group 530
_NGA_G_LOGBOOK_2 _NGA_Group 531
_NGA_G_EVENT_MS _NGA_Group 619
_NGA_G_EVENT_MS_2 _NGA_Group 620
_NGA_G_EVENT_PG _NGA_Group 621
_NGA_G_EVENT_PG_2 _NGA_Group 622

Any ideas why this discrepancy exists and how to fix it? Manually create the required _NGA_G### dps?

[leoknipp]

Maybe there is some information on the internal datapoints different and therefore the groups are not displayed in the table.
You can make an ASCII export of the _NGA_Group datapoints with all configs and try to find differences.

Best Regards
Leopold Knipp
Senior Support Specialist