Haaron Gonzalez Rotating Header Image

June, 2016:

What happens when you accomplish your dreams? Well, you create new dreams

It’s time for me to close a cycle and move on to another endeavor in my career. For the last 3 years I have been lucky enough to work for Konica Minolta formerly known as Hershey Technologies. After Tom Castiglia, Arjay During and Neal Fischer believed in me and gave the opportunity for me to join the team I started engaging with existing/new customers, team members and SharePoint local community folks. I started little by little, building, gaining trust based on pure hard work and consistent outcomes. I was fortunate to partner with account managers and do pre-sale work that help us position our services and close so many deals that with the help of the team we were able to deliver value in a profitable way and consolidate strong/solid relationships with customers. After touching more than 55 customers, more than 74 projects during a 3 year span is time for me to say farewell.

I am extremely proud, grateful and lucky to have the chance to learn from everybody here and to grow professionally accomplishing things that once in my life where dreams and future visions of me. Even do, it’s hard to say goodbye to friends, this is something that I feel and know I need to do. Thanks Konica Minolta formerly known as Hershey Technologies team members, management and top executives for your patience and trust. Please continue taking care of our customers.

What happens when you accomplish your dreams? Well, you create new dreams. That’s why I am joining Slalom Consulting. This is a company with a high level consulting profile that I know is the right step for me to continue doing what I know and what I need to do to strive in bigger challenges and outcomes. I am so excited to join this team, so more histories to come in the future, new dreams and visions to conquer.

Thanks all for your friendship and partnership, sicerelly Haaron Gonzalez

How to display additional lookup data from another list in a Nintex Form

Let’s say that you have a lookup site column that you are using all over the place in multiple lists and sites under your site collection and you need to be able to display additional data from this important list in a Nintex form, there is a way fortunately.

By adding this site column into your content type or list the Nintex Form will identify field as a lookup control automatically and by using the lookup function you can query another list in the site collection and return data from it.

In this example, I have a Stores list, every store has a district number associated, so when I pick and choose a particular store number by using the lookup function I am able to return the district for the selected store.

lookup1

To understand how the lookup function determines what data to bring back, consider the following lookup function:

[code language=”css”]
lookup(“listA”, “ID”, 1, “Title”)
[/code]

This lookup will send a query to SharePoint, asking for list items within a list titled ‘listA’ and return the Title column value from any list items whose ID column value is 1.
Note: The match on the value is case-insensitive.

The lookup function does not support complex query construction; it determines what list items are included, as data to bring back, based on the filter column being an exact match to the value you specify. You can compose complex formulas with the formula builder if you need to build up a complex query, however be mindful that each lookup function will send an individual request to SharePoint for data.

So, in my example I just added a Calculated Value control in the Nintex form and configure the lookup runtime function like this:

[code language=”css”]
lookup("/sites/mysitecollection|mylist","ID",Store,"District")
[/code]

Notice that there is a “|” to point to a list in another site, in this case, the top level site using a relative URL Path, then delimit the list title with a pipe ‘|’ symbol. If your list exists under your current site just use the list title without the URL Path.

lookup2

 

How to read values from query string in a Nintex Live Form

I remember when a friend that was very good at writing technical articles and blog posts told me that he didn’t had the time to do it when I asked why he doesn’t blog anymore. That’s exactly what happened to me in the last couple of months or so. I apologize in advance.

Today, I want to share how you can read query string parameters using JavaScript and pass them into a Nintex Live Form controls.

Set the Client ID JavaScript variable name for your text box controls you want to set with the query string values

  • Select your text box control, right click settings
  • Expand the Advanced section
  • Provide a Client ID JavaScript variable name

Set the Client ID

 

Modify the Custom JavaScript i the form Settings

  • Click the Settings ribbon button
  • Expand custom JavaScript section
  • Create a JavaScript function to read and return query string properties ( I borrowed the function from here)

[code language=”css”]

var getQueryString = function ( field, url ) {
var href = url ? url : window.location.href;
var reg = new RegExp( ‘[?&]’ + field + ‘=([^&#]*)’, ‘i’ );
var string = reg.exec(href);
return string ? string[1] : null;
};

[/code]

  • Invoke the function to get the query string values passing the name of the parameter and use the NWF$ to set the values in the right text box. kmsid is my query string parameter

[code language=”css”]

var surveyId= getQueryString(‘kmsid’);

NWF$(document).ready(function() {
NWF$(‘#’+TitleControl).val(surveyId);
});
[/code]

Custom JavaScript

Now you need to make sure your Nintex Live form URL includes the Query String parameter we are referring in the code. In my case I created a Nintex Workflow that will send an email and in the email body a hyperlink to the Nintex Live form is included. I modified the hyperlink to have my query string parameter kmsid, just make sure you don’t use the default URL provided by Nintex Live, use the resulting URL of your Nintex Live form to construct the entire URL with the additional query string.