Skip to main content

About

About me

Hi there, I'm John - a technology nerd, travel enthusiast and amateur photographer (translation: I like taking photos of landscapes and nature but not very good at it yet).

I'm lucky enough to be able to wake up each morning, go to work and be part of a team that helps make people's life easier through the use of technology like Azure, Office 365 and SharePoint. As a business analyst, my role is to understand the needs of a business and it's users in order to help address a business objective or pain point through the use of technology.

When not working, I like to travel (or plan/dream about my next trip if I'm not already travelling) and experience new places and cultures around the world. My travel style at the moment is to try and get the most out of the limited budget and time by travelling as smartly as possible whilst attempting  experience the best each place has to offer.


About this blog

I'm new to the world of blogging, but created this blog as a place for me to write about things that I'm passionate about ... technology and travel.

I want to use this blog to share things I've learnt throughout my journey in life from little gotchas from technologies that I'm currently using or tips and lessons I've learnt from my travels. I hope it helps you in some way or another whether you came here for technology, travel or both.

I also want to use this blog as an opportunity to improve my writing skills, so any feedback and suggestions.

Feel free to contact me if you have any questions or feedback.

The not so small prints:

  • The views and opinions expressed in my posts are my personal views alone and not that of any other organisations that I may be associated with.
  • If you would like to use content from this blog (full blog posts or photos), please contact me to ask for permission first. Alternatively, sharing or excerpts of content can be used if it is clearly attributed to this blog (via a link to www.johnluangco.com)


Affiliate, sponsored links or contents

For the most part this blog will be paid for using my own money. However from time to time, I may add an affiliate or sponsored link/content into this blog to help subsidize the cost of running this blog (expenses either related to keeping this blog online and costs associated with putting content together).

However be rest assured that any sponsored or affiliate content/link that I place in this blog are here because I:
  • have personally seen, used or experienced the product/service and/or
  • really like using the product and/or 
  • think it will bring value to people reading this blog
In the interest of transparency I will be clear inside any page or posts that contain links or content that contains perks or benefits to me. These will either be identified beside the link and/or flagged at the beggining or end of the post.

My current affiliate channels are:

  • Booking.com
  • Amazon.com

    johnluangco.com is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to amazon.com. Amazon offers a small commission on products sold through their affiliate links. Each of your purchases via our Amazon Affiliate link supports our cause at no additional cost to you.

Popular posts from this blog

Access Web App | Filter a view by current user login (deprecated)

Update (April 1 2017): Microsoft has released an update that willl stop the creation of new apps starting June 2017, and shut down any remaining apps by April 2018. See more here

The problem One of the things I needed to do lately was see if a view within Access Web Apps can be configured to filter data that is related to the logged in user. e.g. as a user I want to be able to view a list of projects where I had been assigned as the project owner.

In SharePoint, this would have been quite easy to achieve as we can create a view and set the filter to {column name} is equal to [me].

Unfortunately Access Web Apps does not quite work this way:

No people picker control in Access Web Apps - this means we need to store and manage our own list of user data within a table in your Access Web App Database (or find a way to link a table with SharePoint's user profile or hidden user information list).Access Web Apps is a relational database - this means the approach to filtering a table view is…

Nintex Workflow | parsing JSON responses from json-only web requests

Update 03/08/16:
Logic Apps has gone GA, and has undergone a major v2 change since this post was written. For the most part, the core actions remain the same but just renamed or work a little differently e.g. http listener (now known as "When an http request is received" + "Received") and conditions (now triggered via the add a condition" button instead of being configured inside the http action.)

It is worth noting that the BizTalk JSON Encoder API app can no longer be found in the marketplace. This is now a native function in Logic Apps. Though, I'll try to refresh this post with the how to do it in the version of Logic Apps that GA'd, I'm not sure when I will have to do it, so if you can't wait, I suggest looking at the xml function can be found here.

Update 07/08/16:
Steps for new Logic App UI that has GA have been added into the solution section below.
The problem
One of the things I have been working on lately in the Nintex Workflow world,…

Azure BizTalk Rules | A Getting Started Guide (deprecated)

Update December 12 2016:It looks like this service has disappeared from the azure portal and documentation that was previously available has also disappeared. 

This connector was developed for v1 of Logic Apps, and whilst Logic Apps has gone on to v2 + general availability, this connector was not one of the connectors that was supported by the current version of Logic Apps. 

I don't know if there is any plans to bring this connector back in the future, but if I see any updates, then I will update this post. 

One of the things I've been playing around with lately is the Azure BizTalk Rules API App from Azure (currently in public preview). BizTalk Rules has been around since BizTalk Server 2004, however the server offering for BizTalk required a large upfront investment in terms of cost as well as skills required to effectively leverage the tool.

The introduction of several BizTalk capabilities as a PaaS (Platform as a Service) offering in Azure is intended to make the capability …