how to set a geolocation field in Nintex Workflow

Try 0.22631S 51.49561E

this is how the mobile app delivers it, hopefully it is the same

interesting ...

I attempted to follow the stpes in this blog SharePoint Map View for Picture Library with automatic geolocation from EXIF data - Ian's SharePoint Blog

but in a Nintex workflow : failed (same error message about PrimitiveValue) and when doing the same Set Field but in standard SPD Workflow 2010 = success !

So.. is there something fishy about setting a Location field type value in Nintex Workflow for Office 365 as opposed to the same in SPD ?

I shall email Nintex Support.

I also contacted a TE for some more information. I will forward if I receive anything.

Sean Fiene​ and I took a look and can't seem to replicate the issue.  My thought would be it has something to do with the version of NWF or SharePoint. What versions are being used as it may be something that doesn't show up in newer builds.

I realize this is an older post, but in case anyone else is having the same issues we did, I'll detail how we came to our solution.

SharePoint 2013 On-Prem - Nintex Workflow 3.2.5.0

Goal

Use a Nintex workflow to populate the Location (Geolocation) field in a library where the longitude and latitude are automatically pulled from the photo.

I'm not going to into how the data is pulled from the photo, because that part was already setup for our situation and I don't know how it works. Our process also had calculated fields to give us the values for longitude and latitude.

Longitude Calculation:

=IF(RIGHT(wic_System_GPS_Longitude,1)="E",Degrees_Long+(Minutes_Long/60),(Degrees_Long+(Minutes_Long/60))*-1)‍

Latitude Calculation:

=IF(RIGHT(wic_System_GPS_Latitude,1)="S",-(Degrees_Lat+(Minutes_Lat/60)),Degrees_Lat+(Minutes_Lat/60))‍

In our specific situation, there was already a SharePoint Designer workflow for this process. We tried to recreate it verbatim into Nintex, but it didn't work. We found that the Designer workflow used the "substring from index (starting at 8)" process (detailed here on technet). We found the substring portion was no longer necessary.

So, it was as simple as grabbing the longitude and latitude directly from the calculated fields. We no longer had to worry about the "float;#" problem others had in the past.

We did have one caveat though. In trying to populate the "Point ({longitude field} {latitude field})" value directly in the Update Item Nintex action as the Value, it failed. The only way we were able to get it to work was to use the Build String action, build the exact same string value and store it into a variable. Then populate the field with the variable.