Skip to main content
Nintex Community Menu Bar
Solved

NWC Workflow with Start Event SharePoint - New list item: How to get the managed metadata field?

  • December 1, 2021
  • 9 replies
  • 307 views

tiwookie
Forum|alt.badge.img+3

Hey nintex community,

 

I'm currently trying to build a workflow onto a SharePoint Online document library. Therefore I need all the item metadata to process and play with in my workflow.

 

My Start Event is the "New list item" creation. Through this I get the coresponding Start Event start variables, so the values of each column of the item - with the ecxeption of the managed metadata fields. They do not appear in the list.

 

I've done some research, but didn't find any info on that. Can anyone point me in the right direction in how to get the managed metadata info?

 

Thanks and kind regards!

Tim

Best answer by JRoberts

Give these steps a try. I know it's not the most optimal to re-retrieve the list item even though it may already be available in the Start Event, but you can get the Metadata Label field this way.

 

 

1. Use the "Retrieve an item" action to retrieve the current item that starts your workflow.

2. Set the Item ID based on the start event ID variable that triggers your workflow.

3. Store the result in an object variable for that list/library item. 

 

From there you can get to the metadata fields Label variable which stores a semi-colon delimited list of your selected metadata values:

 

 

Results:

 

You can also use the Apply a regular expression action to take the metadata variable's delimited text string and load it into a collection using the Split option with a semi-colon. From there you can work through the list as needed.

 

 

 

 

Hope that helps!

 

View original
Translate
Did this topic help you find an answer to your question?

9 replies

JRoberts
Nintex Employee
Forum|alt.badge.img+12
  • Nintex Employee
  • 62 replies
  • Answer
  • December 2, 2021

Give these steps a try. I know it's not the most optimal to re-retrieve the list item even though it may already be available in the Start Event, but you can get the Metadata Label field this way.

 

 

1. Use the "Retrieve an item" action to retrieve the current item that starts your workflow.

2. Set the Item ID based on the start event ID variable that triggers your workflow.

3. Store the result in an object variable for that list/library item. 

 

From there you can get to the metadata fields Label variable which stores a semi-colon delimited list of your selected metadata values:

 

 

Results:

 

You can also use the Apply a regular expression action to take the metadata variable's delimited text string and load it into a collection using the Split option with a semi-colon. From there you can work through the list as needed.

 

 

 

 

Hope that helps!

 

Translate

tiwookie
Forum|alt.badge.img+3
  • Author
  • Rookie
  • 11 replies
  • December 3, 2021

Wow, @JRoberts, what a perfectly described and illustrated solution! Thanks for your fast help here, it worked like a charm!

 

Kind regards and happy weekend!

Tim 

Translate

JRoberts
Nintex Employee
Forum|alt.badge.img+12
  • Nintex Employee
  • 62 replies
  • December 3, 2021
Glad to help!
Translate

Forum|alt.badge.img+5
  • Apprentice
  • 30 replies
  • February 8, 2023

As this is a suitable workaround, why in the world the StartEvent does not contain all fields from a given list or library?

As it can be done with a “Retrieve an item”-Action, it may has no technical reason.

Are there any plans to fix this bug (you may call it a limitation)?

Please excuse my impatience, but moving a corporate farm to NAC and encountering a new obstacle every day can be very frustrating.

With kind regards, Ronny

Translate

Forum|alt.badge.img+5
  • Apprentice
  • 30 replies
  • February 8, 2023

When using “Retrieve an item”-Action, I do not get the Label fields as in your screenshots.

If I log the field values, I get:

Sprache: {"WssId":1,"TermGuid":"80f11bae-9a87-46c8-8025-f1f5f0488d52","Label":"1"}

 

Another obstacle, I will open a case.

 

With kind regards, Ronny

Translate

rickdemarco
Nintex Employee
Forum|alt.badge.img+8
  • Nintex Employee
  • 69 replies
  • February 10, 2023

@RonLevy There reason why MM and Lookup columns are not part of the start event data is because it’s a technical limitation on the API side otherwise we would of certainly provided it. The retrieve was the only option available.

If you have any other specific isses around the SharePoint connectors or events please feel free to contact me directly at rick.demarco@nintex.com

Cheers, Ric

Translate

Forum|alt.badge.img+5
  • Apprentice
  • 30 replies
  • February 10, 2023

@rickdemarco Thanks for your quick response. I opened a ticket and had a Teams-Session yesterday. Nintex is trying to replicate the issue. It is not solved until now. It may has to do with our default language (site and term-store). Thanks for the offer. All the best, Ronny

Translate

Forum|alt.badge.img+5
  • Apprentice
  • 30 replies
  • February 28, 2023

@rickdemarco : Nintex has confirmed, that this is a bug and it has indeed to do with the language.

While it's not guaranteed, they expect the fix to be rolled out in couple of weeks. 

Nintex Support Case #00530600

Cheers, Ronny

Translate

Forum|alt.badge.img+5
  • Apprentice
  • 30 replies
  • March 21, 2023

The fix has been released. Issue is solved. Wonderful, thanks Nintex

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings