Azure component that compares 2 word documents? - azure

I am looking to build a solution where we can compare (Automated) a word document we email to a client to the word document the client emails us back.
Any suggestions please, we will be using MS Azure to create the solution.

Due to the lack of a direct automation of this feature you can use an indirect route to approach the solution.
Note:
This solution invokes Word using COM automation. Hence this is expected to be running on a VM that has word installed.
Since this solution simplifies the content that is being compared, it might lose the details you might want to show up in your comparison.
You can create a PowerShell script that does the following
Convert the documents to a simpler (txt) format - See this or this.
Compare the text files - See this.
The powershell script will get the comparison done. After that its up to how much fancy you want to get when exposing this functionality outside that VM. e.g. You could create an HTTP invokable API that can call this Powershell script and return results.

I think your best bet would be using Microsoft Azure Logic Apps! Azure Logic Apps allows you to develop advanced automation workflows on the cloud and it supports a vast array of connectors out of the box including email triggers and the Microsoft Word Connector. If that's not enough then, you could even develop your own connectors too...

Related

Data extraction using Azure Cognitive services

Goodday!
I've got a library full of documents. I would like to be able to know some more about these documents without reading through all of them. On the first page of each document I already put some relevant information about the document such as year of creation, author, number of pages and confidentiality.
I want to use some AI to browse through these documents and decide which is what and return it to me so I can store it in a CSV or something. This way I'll be able to easily find the right document.
Now, I did use LUIS and some of the TAA service of Azure's cognitive services before. But I cannot figure out a way how to accomplish this.
Is it theoretically possible to send the first page (using a powershell script to cut the rest of the document and send it through) to LUIS, which can then return the entities? I'd like them in a way: Date of creation: 18/10/2018, pages: 100.
Or is there a better way to use Azure's powerfull AI to get this done?

Microsoft Navision and Odata Uri via Excel webservices function

So, I'm working on developing some business apps for my organization, and I've been trying to implement the usage of the Navision Web Api for external reporting. And Unfortunately, I'm stuck using Excel because of traditional antiquated business practices.
My question - is there any way to drill-down to single values or even access the json payload through excel's web services function. I've tried switching the payload to XML on OData v4, but I can't get that to work. This is driving me insane - I cant even think about another Pivot table via odbc sql, or Odata, because I know there's a better way. I'm pretty good with PowerShell, javascript, html etc.. but Im almost clueless when it comes to VBA, and it just seems like to much suffering. Anywho, if I cant use the OData feed in the web services function - well why? Is Microsoft just trying to screw us? I keep getting a value error - naturally - because I cant drill down to a single value, format to xml, or access the json object within the web services function(if it even exists in there??) here's a link to what im looking to do Excel Services function Demo- except I cant do it - so is there any substitute or solution.
So, stop whining and use power query to fetch data from Nav’s OData endpoint.

Accessing source code of PowerApps and hosting it elsewhere

We are looking into using PowerApps to develop apps quickly. However, we are concerned about dependency on Azure and inability to access the source code.
We are interested in understanding the transportability of an app in PowerApps.
1) Can we access the source code?
2) In a scenario where PowerApps does not satisfy our needs, can we take away the source code and manage everything ourselves?
3) Can we deploy the code in another cloud provider such as AWS or Google Cloud or our own server?
Thanks!
Can we access the source code for Power Apps?
Yes. You can use export to zip.
Inside the zip there's a .msapp file. You also unzip that.
There's a ton of json files. It includes your Power Apps code.
See also:
running a diff on two Powerapps: https://github.com/microsoft/powerapps-tools#powerapps-review-tool
A Flow / Power Automate that exports your code to github: https://github.com/SeaDude/seattlePowerAppers/blob/master/outlines/powerappsVersionControl.md
No, you cannot access the source code. The whole point of PowerApps is that it is a zero code environment. Therefore you cannot take the code and use it elsewhere.

Spotfire Automation

Is it possible to automate the publish of dxp file to the server. What I want to achieve is build a command line tool, user navigates to the dxp file and runs a command (let's say publish), this should save the file to the library without opening spotfire client (something similar to running spotfire in Headless mode).
I got to know that Spotfire Automation Services can be of some help in this task, but I have never used the automation services and don't know how to install or find the automation services module. Any help or direction is highly appreciated. Thanks
Automation Services is a licensed framework from TIBCO that lets you automate several tasks including Open or Save analysis to library, replace or remap data sources, run alerts etc.
But if your sole requirement is to publish analysis to library then use the import-library-content on command line, or save it in a batch file and use IronPython to trigger that as using button from the DXP.
See API docs of import-library-content for usage.
you can check Google for Automation Services and see more details on its capabilities, but I'm pretty sure your use case is covered. Spotfire does not offer this feature out of the box (except maybe using the admin command tool, but that'd only be for admins).
your organization will need to buy a license for AS, since it's a separate product in the Spotfire suite. talk to your TIBCO rep or send me a PM.
Yes, you can use Automation Services for this. Automation Services needs to be licensed from TIBCO, but it provides a framework that will allow you to create job.xml files which specify a list of tasks for Automation Services to execute. You can then submit the job file to a web service when you want the tasks to be executed.

Permissions problems with Excel Services in SharePoint

I'm trying to implement an Excel Services reporting solution in SharePoint (MOSS). Since the source data is a SharePoint list, this problem is doubly frustrating. I keep bumping up against permissions problems, even though I've enabled virtually everything in sight.
The first error is about refreshing external data - it's not (really) external data, but that's a semantic point.
The second error is a cryptic "Excel Web Access" problem.
Anyone get this to work??
Could be a couple different problems. The first possibility is that Excel Services doesn't support using SharePoint list data (crazy I know)... although this only applies if you try using the type of embedded data source you get if you choose Export to Excel from a list (again, I know crazy).
However an easy way around this problem is to use the SP webservices to get you list data. I had a macro written by someone at MS a while back that automated this conversion, if I canfind a link I'll post it. If you are using Kerberos then you task is probably finished. If using NTLM then you may need to also configure an SSO application so that the right credentials can be passed to the webservice (or any other data source for that matter). There's a pretty good step by step here.
One kind of "hack" to get this to work via UDF's (which if trusted, custom code can be deployed and made available via Excel Services) can be found here.

Resources