Duplicate GraphPOID while creating map using Orion SDK

viv1singh

Hi Team,

I am currently automating map creation using a Python script in conjunction with the Orion SDK. While I am able to generate the maps successfully, they are all being created with the same GraphPOID. This issue is causing problems with map status monitoring and results in references in a parent map pointing to a single map.I would like to know how to generate maps with unique GraphPOIDs. Any guidance would be greatly appreciated.

jeremymayfield

You are encountering duplicate GraphPOID values because your Python automation is likely reusing the same Container/Graph definition object when creating maps through the SolarWinds Orion SDK.

In SolarWinds Orion Platform (modern Maps subsystem), GraphPOID is not something you manually generate. It is:

• Automatically assigned
• Derived from the created Orion.Maps.Graphs record
• Linked to a unique Container/Map entity

If multiple maps are receiving the same GraphPOID, it typically means: You are creating multiple Containers that reference the same underlying Graph object. This is a creation logic issue, not an SDK limitation.

Understanding GraphPOID

Internally:

• Orion.Maps.Graphs → contains the graph definition
• Orion.Maps.Containers → represents the map container
• GraphPOID → pointer linking Container to Graph

If you:

• Clone an existing map JSON
• Reuse a previously created Graph ID
• Copy a Container definition without creating a new Graph record

You will duplicate the GraphPOID.

Root Cause (Most Common)

Your script is likely doing one of these:

Pattern Causing Duplication

1. Query existing Graph
2. Reuse its GraphID
3. Create new Container referencing that Graph

Result: Multiple maps → one Graph → same GraphPOID

Correct Map Creation Pattern

You must:

1. Create a NEW Orion.Maps.Graphs record
2. Use the returned GraphID
3. Create a NEW Orion.Maps.Containers record referencing that new GraphID

Every map must have:

Unique GraphIDUnique ContainerIDUnique GraphPOID

Correct Python SDK Workflow

Step 1 — Create Graph

graph_props = {    "Name": "My New Map Graph",    "Description": "Auto-generated",    "Definition": json_definition_string}graph_uri = swis.create("Orion.Maps.Graphs", **graph_props)

This returns:

swis://.../Orion.Maps.Graphs/GraphID=<X>

Extract GraphID.

Step 2 — Create Container

container_props = {    "Name": "My New Map",    "GraphID": graph_id,    "Owner": "admin",    "IsFolder": False}container_uri = swis.create("Orion.Maps.Containers", **container_props)

This generates a new ContainerID and new GraphPOID automatically.

What NOT To Do

Avoid:

graph_id = 253   # Hardcoded or reused

Or cloning:

existing_graph = swis.query(...)

Then reusing that GraphID. That guarantees duplicate GraphPOID.

How to Validate the Issue

Run:

SELECT GraphID, COUNT(*)FROM Orion.Maps.ContainersGROUP BY GraphIDHAVING COUNT(*) > 1

If results return:

GraphID = 253Count = 5

That confirms duplication is due to reuse.

If You Are Cloning Maps

If your goal is to template maps:

Correct pattern:

1. Retrieve Definition JSON from template
2. Modify JSON as needed
3. Create NEW Graph using modified JSON
4. Create NEW Container referencing that Graph

Never reuse original GraphID.

Why Status Monitoring Breaks

Parent maps reference GraphPOID. If multiple maps share same GraphPOID:

• Status calculation collapses
• Parent references become ambiguous
• Monitoring engine evaluates one graph only

This is expected behavior when Graph objects are reused.