TIDBITS on the Microsoft Power Platform

Dynamics 365 Relationship Sales and LinkedIn's Sales Navigator

One of the huge shifts and benefits for a sales person is when technology gets aligned so that keeping data current falls to the most logical location. Consider for instances a prospects name, company and job title. A shift is when this information is kept current by that specific prospect rather than the sales person following that prospect. The prospect updates their name, role and company information because it is beneficial to the work that they are doing. The sales person who has a relationship with this person, or who is following them, can then be a straight consumer of data managed by a logical source.

Now this isn't perfect .. not everyone updates their information even with the power of a product such as LinkedIn and Sales Navigator so technology still needs to take another step in validating that the data is current. A futuristic option on this will be when AI technologies can tap into larger or the largest data repositories and filter out what they need to validate a person's name, role and company. If we take this one step further we add address, telephone numbers, historical information.

Data exists, we can purchase this data, but we are not quite to the point where the data on a person is 100% transparent when we need it AND there are many reasons why this also sends chills up many a spine. 

If we circle back to what is happening in the world of Microsoft Dynamics 365 for Sales we find that Relationship Sales is a combination of the knowledge within LinkedIn and the Power of the Dynamics 365 platform. 

Unifying the best of both worlds to further empower the business sales teams. It also uses AI Technology in addition to the combination of data. This takes this one step further.

Take a Peek 

Products, 3D 360 Degree Mixed Reality and Product Visualize

At the Microsoft Business Applications Summit this week I had a chance to take a look at and discuss Microsoft Product Visualize. I loved seeing how it worked, but more importantly I had dug into the details of where data is stored and how is it created. 

So first What is Microsoft Visualize? 

Consider the Microsoft Dynamics Product Catalog. You have a list of products associated with an opportunity and each item has a description. This doesn't really offer the most efficient way to quickly grasp all that you want to know. We then consider the flat, 2D ability to add a picture. Great! Wonderful, but can we do more? This is where Product Visualize for Dynamics 365 comes into plan. 

I have my Tablet (Surface/iPad/etc), I am at a client site and I am discussing an opportunity that includes a number of products. I might even have two similar products, because my prospect or client has not decided on what they want.  Product Visualize offers not only a 3D Image of the product, but it offers the ability to show a full 360 Degree 3D View of the product depending on how the "user" (myself, the prospect or customer) moves the tablet. 

So how does Product Visualize technically do this? 

Product Visualize uses a product .glb file stored in an integrated SharePoint library. The library that can be configured when Dynamics 365 is setup and configured. The file contains the 3D model saved in GL Transmission Format (glTF).  gITF offers the ability to store such information such as node hierarchy, cameras, materials, and animations and a GLB file is the binary version of .GLTF files.  

Note: For those of you who are old hands at gITF and glb, please feel free to expand on this.. 

BUT how do we actually get the images and the data for the GLB file? 

I have my product and I have Dynamics 365 for Customer Engagement, but I don't have a glb file. This is where the growing momentum in partnerships between the new worlds within the graphical industries and the ever evolving world of customer engagement becomes a huge win/win.