Trimble Connect User Forum

Can anyone help me troubleshoot this error? It's clearly something with the psets but I'm lost on next steps. 

HTTP 400 (Bad Request): Provided list of psets identities contains duplicates

See attached for my set up of the pset. These are applied at both the part and assembly level to aid with approval tracking between four different parties Team A, B, C, and D (C and D not shown in screenshot). 

Hi Ryan,

My first guess is that the request to assign property sets to multiple elements contains duplicates. If the "link" values (of each property set in the operation) contains duplicates then maybe you get this error.

Are you getting this when using the Properties Panel of Trimble Connect for Web? If yes - I'd be surprised as it should handle this case - then the network traffic in Developer Tools could reveal what data is sent to the service that generated HTTP 400.

Can anyone help me troubleshoot this error? It's clearly something with the psets but I'm lost on next steps. 

HTTP 400 (Bad Request): Provided list of psets identities contains duplicates

See attached for my set up of the pset. These are applied at both the part and assembly level to aid with approval tracking between four different parties Team A, B, C, and D (C and D not shown in screenshot). 

Thanks, Tibor. I will give that a look. And, yes, I am getting this when using the Properties Panel of Trimble Connect for Web. Specifically, I am getting this when I am attempting to apply an organizer across multiple models. 

Hi Ryan,

My first guess is that the request to assign property sets to multiple elements contains duplicates. If the "link" values (of each property set in the operation) contains duplicates then maybe you get this error.

Are you getting this when using the Properties Panel of Trimble Connect for Web? If yes - I'd be surprised as it should handle this case - then the network traffic in Developer Tools could reveal what data is sent to the service that generated HTTP 400.

Can anyone help me troubleshoot this error? It's clearly something with the psets but I'm lost on next steps. 

HTTP 400 (Bad Request): Provided list of psets identities contains duplicates

See attached for my set up of the pset. These are applied at both the part and assembly level to aid with approval tracking between four different parties Team A, B, C, and D (C and D not shown in screenshot). 

Hi Ryan,

Let me know if I imagine the workflow correctly:

• you have N models
• you linked various objects from the models to organizer groups (or it was done automatically in case of a rule-based group)
• you selected an organizer group => the linked objects were seleted in 3D
• you opened the Properties Panel and tried to add your property sets to the selection (Add Properties menu point in Properties Panel).

If the above is kind of close to your workflow, then there is a chance that it can cause the mentioned error, although I am was certain that the scenario is handled well.

The duplication of pset identities can happen if you have objects with the same guid in more than one model. The links in the organizer groups contain only the guid information, not the model id. This is by design. As a consequence, when you select the organizer group the duplicated guids are selected in 3D in every loaded model. You can see this by looking at the organizer group's link count and the selection count. Selection count is bigger in this case.

Still, it is curious how the bug happens, because the Property Panel should handle this situation too.

Thanks, Tibor. I will give that a look. And, yes, I am getting this when using the Properties Panel of Trimble Connect for Web. Specifically, I am getting this when I am attempting to apply an organizer across multiple models. 

Hi Ryan,

My first guess is that the request to assign property sets to multiple elements contains duplicates. If the "link" values (of each property set in the operation) contains duplicates then maybe you get this error.

Are you getting this when using the Properties Panel of Trimble Connect for Web? If yes - I'd be surprised as it should handle this case - then the network traffic in Developer Tools could reveal what data is sent to the service that generated HTTP 400.

Can anyone help me troubleshoot this error? It's clearly something with the psets but I'm lost on next steps. 

HTTP 400 (Bad Request): Provided list of psets identities contains duplicates

See attached for my set up of the pset. These are applied at both the part and assembly level to aid with approval tracking between four different parties Team A, B, C, and D (C and D not shown in screenshot). 

Yeah, you're spot on with my workflow. What's odd though is that we have another site working an identical project and they are taking the same approach that I am and have not encountered this issue. I did a GUID export from the data table with two models open and no duplicate GUIDs appear yet I still encounter that error when I try to apply to the 2nd model. 

Hi Ryan,

Let me know if I imagine the workflow correctly:

• you have N models
• you linked various objects from the models to organizer groups (or it was done automatically in case of a rule-based group)
• you selected an organizer group => the linked objects were seleted in 3D
• you opened the Properties Panel and tried to add your property sets to the selection (Add Properties menu point in Properties Panel).

If the above is kind of close to your workflow, then there is a chance that it can cause the mentioned error, although I am was certain that the scenario is handled well.

The duplication of pset identities can happen if you have objects with the same guid in more than one model. The links in the organizer groups contain only the guid information, not the model id. This is by design. As a consequence, when you select the organizer group the duplicated guids are selected in 3D in every loaded model. You can see this by looking at the organizer group's link count and the selection count. Selection count is bigger in this case.

Still, it is curious how the bug happens, because the Property Panel should handle this situation too.

Thanks, Tibor. I will give that a look. And, yes, I am getting this when using the Properties Panel of Trimble Connect for Web. Specifically, I am getting this when I am attempting to apply an organizer across multiple models. 

Hi Ryan,

My first guess is that the request to assign property sets to multiple elements contains duplicates. If the "link" values (of each property set in the operation) contains duplicates then maybe you get this error.

Are you getting this when using the Properties Panel of Trimble Connect for Web? If yes - I'd be surprised as it should handle this case - then the network traffic in Developer Tools could reveal what data is sent to the service that generated HTTP 400.

Can anyone help me troubleshoot this error? It's clearly something with the psets but I'm lost on next steps. 

HTTP 400 (Bad Request): Provided list of psets identities contains duplicates

See attached for my set up of the pset. These are applied at both the part and assembly level to aid with approval tracking between four different parties Team A, B, C, and D (C and D not shown in screenshot). 

Hi Ryan,

I'm out of ideas. If you are familiar with the browser DevTools - and there with the network tab -, I suggest inspecting the network call that reads that scpecific organizer group, and then the network call that tries to create the property sets.

You'll have to filter the network calls to show only calls to the organizer service ("org-api" filter would do I think), and then calls to the property set service ("pset-api"...). You'll see several unrelated calls even with these filters.

It is easier to get what interests you if you clear the network calls list, then do a Refresh in the Organizer panel (you'll see the network calls for each group). Then possibly save the involved data somewhere, do the selection, Property Panel open. Then clear the network calls again and try the pset creation.

If it's not working then please create a support ticket. There you can add more sensitive information (network logs for ex). The more details the better.

Yeah, you're spot on with my workflow. What's odd though is that we have another site working an identical project and they are taking the same approach that I am and have not encountered this issue. I did a GUID export from the data table with two models open and no duplicate GUIDs appear yet I still encounter that error when I try to apply to the 2nd model. 

Hi Ryan,

Let me know if I imagine the workflow correctly:

• you have N models
• you linked various objects from the models to organizer groups (or it was done automatically in case of a rule-based group)
• you selected an organizer group => the linked objects were seleted in 3D
• you opened the Properties Panel and tried to add your property sets to the selection (Add Properties menu point in Properties Panel).

If the above is kind of close to your workflow, then there is a chance that it can cause the mentioned error, although I am was certain that the scenario is handled well.

The duplication of pset identities can happen if you have objects with the same guid in more than one model. The links in the organizer groups contain only the guid information, not the model id. This is by design. As a consequence, when you select the organizer group the duplicated guids are selected in 3D in every loaded model. You can see this by looking at the organizer group's link count and the selection count. Selection count is bigger in this case.

Still, it is curious how the bug happens, because the Property Panel should handle this situation too.

Thanks, Tibor. I will give that a look. And, yes, I am getting this when using the Properties Panel of Trimble Connect for Web. Specifically, I am getting this when I am attempting to apply an organizer across multiple models. 

Hi Ryan,

My first guess is that the request to assign property sets to multiple elements contains duplicates. If the "link" values (of each property set in the operation) contains duplicates then maybe you get this error.

Are you getting this when using the Properties Panel of Trimble Connect for Web? If yes - I'd be surprised as it should handle this case - then the network traffic in Developer Tools could reveal what data is sent to the service that generated HTTP 400.

Can anyone help me troubleshoot this error? It's clearly something with the psets but I'm lost on next steps. 

HTTP 400 (Bad Request): Provided list of psets identities contains duplicates

See attached for my set up of the pset. These are applied at both the part and assembly level to aid with approval tracking between four different parties Team A, B, C, and D (C and D not shown in screenshot).