I have created a plugin using the CRM SDK which gets an attchment from a CRM annotation and emails it to a user.
The code I have written works well when running locally within a web app but once I run it as a published plugin the email looses the attachment.
Any ideas?
what do you mean as a published plugin? how else were you testing it, do you mean a different deployment i.e. IFD / On Premise?
i would check the trace logs and see if the plugin has caused an errror, also make sure how the plugin is authenticating - who is it being run as and whether they have the necessary permissions.
Related
PayPal has an activity report under the 'Reports' tab on the website. We're wondering if it would be possible to generate this report and download it using an API. We have a program that imports the report into our system but don't want the risk of putting in the wrong dates and the hassel of manually downloading the file every time.
After researching the PayPal API all I can find is a thing called PayFlow, which seems to be for a different purpose.
Any solutions for this?
if you have enabled your business by integrating with PayPal Payments Pro then you can make use of the Payflow Reporting API.
This is applicable only if you have a Payflow Account.
I had submitted a Teams App for approval. The approval has Failed with primary reason being "We could not install your app"
I would like to know how exactly the app is tested. I had submitted a zip file containing the manifest.json as part of the submission. How is the validation team going about using the zip file and manifest.json? I am able to install the app(bot) without any issues with my test accounts for 1:1 chats. If the validation team can let us know the steps they are following to test the app, then we can try replicating those to see if we get the same error.
The testing procedure in the Microsoft documentation is as mentioned in this link: https://msdn.microsoft.com/en-us/microsoft-teams/botsadd#adding-a-bot-for-11-chat-only
Is the validation team is trying to sideload the app into a team as a result of which they are seeing an error on installation. The app is not meant for use in teams. It is for use in 1:1 chats only. Listing the steps that the validation team is following will be of much help!
All Teams apps must be packaged and sideloaded per instructions on MSDN:
Packaging: https://msdn.microsoft.com/en-us/microsoft-teams/createpackage
Sideloading: https://msdn.microsoft.com/en-us/microsoft-teams/sideload
The 1:1 testing link you refer to is only for that: local testing. For apps submitted to the store, you need to follow the above steps.
In other words, sideload the same app package you want to upload to the store. Does it load?
A couple things to check:
To ensure your manifest is well structured, use the schema Intellisense tip mentioned here: https://msdn.microsoft.com/en-us/microsoft-teams/schema
There is a known issue with description.full length - keep it under 255 characters for now.
I am testing web application using Cucumber. There's certain link on the web page when clicked will trigger Microsoft Outlook to create an email to be sent to someone.
How do I switch from web browser to Outlook email window created from Outlook? Check the Subject? Check the To: (email recipient)? Close the email window, switch back to web browser and pass the Then test.
what sort of libraries and methods do I need to use?
This cannot be achieved with Selenium WebDriver/Capybara/Cucumber.
You can potentially use Outlook 365 (the online version of Outlook) to log in and automated your verification on the email. It's possible that you may run into captchas there though.
Personally I have emails delivered to a mailinator account. I check an inbox there to verify end-to-end email deliveries. This has worked for me. This allows for complete integration testing of frontend/backend/smtp components.
You can't do this with Capybara. I suggest checking the content of the mailto link.
I am trying to build my own WOPI host using ASP.NET MVC and its WebAPI functions according to this example
https://code.msdn.microsoft.com/office/Building-an-Office-Web-f98650d6
I successfully used that example to connect to my Office Web App Server and I can use that to access files of Excel and PowerPoint in local path and I am able to edit it, but I cannot use it to open word document in editing mode as the Post action handler isn't implemented completely without any response so that it cannot handle any edit request.
In order to add support for editing of Office document, I tried this example with POST request handler based on Cobalt library extracted from Office Web App Server.
https://github.com/marx-yu/WopiHost
With this example I managed to edit ans save all kinds of document with Office Web App Server. However, when I tried to integrate these two together I found that even if I can enter the edit window of Excel and PowerPoint and I can see that Post Requests from Office Web App Server like locking and Cobalt are handled by my WOPI Post API action handler. Those change doesn't take any effect on my local file at all. Moreover, I still cannot edit word document and when I checked the back log of Office Web App Server, I found the error message is Cobalt is not supported while I have already set the SupportsCobalt in CheckFileInfo response to true! Any help is very appreciated!
I think I have exactly what you are looking for. Check out my implementation of the WOPI host. It's an MVC6 app that takes the best from the both examples you are referring to and adds some extra features.
Recently announced at Microsoft Build is the ability to convert an existing ASP.NET Web API to an Azure Mobile Service. I was curious as to if anyone has successfully done this yet, and the steps needed to do so.
Things I've tried thus far:
Added the Azure Mobile Service .NET Backend & Azure Mobile Service -
Entity Framework Nuget Packages to my existing ASP.NET Web API
project.
Resolved an issue with OWIN and AMS(ZUMO) conflicting Startup.cs assemblies.
Ensured the ASP.NET Web API compiles locally, and published as an Azure Mobile Service.
However whenever publishing, it seems I only get a runtime error on the server.
Here was the best example of potentially doing this: http://channel9.msdn.com/Events/Build/2014/3-623
Secondly I've looked a bit into just running the OWIN pipeline via: http://www.strathweb.com/2014/02/running-owin-pipeline-new-net-azure-mobile-services/
I know that this is in a preview mode, but figured some document trail would help!
Can you try adding your existing WebAPI assets to Mobile Services project you create from VS? This will make sure all the right things are wired up. Also, check the Logs tab in the portal for any clues.
This should help..
http://blogs.msdn.com/b/azuremobile/archive/2014/04/10/creating-an-azure-mobile-services-net-backend-from-scratch.aspx
Thanks
Supreet