I'm trying to use the QBO Rest API to insert invoices into our system and want to use the BillEmailCc attribute of invoices. I've read on their site that these are only available for minor version 7. I've try setting the minor version in my queries but still I get errors saying this attribute is not valid. How can you access the minor version 7?
url: https:https://sandbox-quickbooks.api.intuit.com/v3/company/193514338926917/query?query=SELECT%20BillEmail%20FROM%20Invoice%20WHERE%20CustomerRef%20%3D%20%2760%27&minorversion=7
After doing some digging in the console, I deduced that the fields to set are as follows
"AllowOnlinePayment":true,
"AllowOnlineCreditCardPayment":true,
"AllowOnlineACHPayment":true,
Quickbooks support has said these attributes aren't supported, however.
Related
I have a task where I need to use ARM template to "setup SQL server with elastic pool and 2 databases (imported from bacpac files) use Microsoft Adventureworks samples."
Most of the template I made using "101-sql-elastic-pool-create" template that is available here: https://github.com/Azure/azure-quickstart-templates/tree/master/101-sql-elastic-pool-create
I used it for the elastic pool setup and used a sample from this documentation (https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-deploy-sql-extensions-bacpac) to have the .bacpac imported to the database
But when I try to deploy this template (the template is available to see here: https://github.com/KarlisAG/SQL_ARM/blob/main/azuredeploy.json ) it throws me an error
("Resource Microsoft.Sql/servers/elasticPools 'task4sql/elasticp' failed with message '{ "code": "BadRequest", "message": "An error occurred while processing this request.", "target": null, "details": [], "innererror": [] }' ")
So, the biggest problem is (besides me being an absolute newbie) not knowing what I need to fix, because there is no additional information granted, besides the "BadRequest". For deployment I used two different methods: 1) the automatically generated one from VS when created Azure resource groups, 2) One shown in this documentation, with few of my own changes, so it could work for me ( https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-deploy-sql-extensions-bacpac#deploy-the-template ), from where I also got the code part for importing .bacpac to my newly created database. [Both of the are available at the same repository, named "Deploy-AzureResourceGroups.ps1" and "DeployScript.ps1" respectively].
Both of the methods return the same error.
I even manually created these things in Azure portal to see what their template looks like and maybe copy some things that are not present in my template, but from what I saw I have exactly what they automatically generate.
And when I checked the deployment status in Azure portal I can also see that during the elastic pool creation it fails: screenshot from that section available here
So does anyone know how should I have created this type of template, or did I recreate it poorly, or am I missing some small mistake that keeps blocking me?
So after multiple tries it seems that I finally figured out what I was doing wrong. I am still not sure which of the changes made a difference, besides the last one, so I will write what I changed, so other people who could be facing similar issue know what they could do fix the issue.
At first, after #stringfellow noted, I thought that Free Trial is restricting me from doing anything, but after I lowered my DTU multiple times, to the point where it was at 5 (starting from 100), the same issue persisted, so probably it was not the issue (later on I had to change it at minimum to 50). I also changed the Elastic Pool edition from Standard to Basic. But doing these changes still didn't fix the issue.
At last, after answering #NachoMartínez-Aedo comment about the api version, it got me thinking. Because in the code that I posted I used "2020-08-01-preview" api version, but in reality I used "2014-04-01-preview", because when I changed the api version of all my parts to the 2020 one, then powershell told me that (No registered resource provider found for location 'northeurope' and API version '2020-08-01-preview' for type 'servers/databases/extensions'. The supported api-versions are '2014-01-01, 2014-04-01, 2014-04-01-preview'.). And after reading through that again and remembering that when I was looking at some documentation and Azure portals automatically generated templates I knew that I always say them using the 2020 api, not the 2014, which left me confused as to why I couldn't also use the newest version. And reading that error again I saw, that it specifically told that 2020 api version was not supported for the type "servers/databases/extensions", not that all of the parts must be in 2014 version (which is what I thought when I saw that error), so I tried and changed all the 2014 back to 2020 and left the extension api back at 2014 (previously I thought that all api versions should be the same, not sure why, maybe because most of the examples and documentation had everything have the same api version) and the everything worked, even the import part, about which I was worried.
So in the future I am not too sure if there is a better/newer way to import .bacpac file to newly created database with ARM, or just have to leave it as is and in the future use this same approach. Does anyone know?
I got the import extension from here: https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-deploy-sql-extensions-bacpac
, where they use examples with 2014 api for the extension, so because of that I tried to use it for all my parts, but only during this answer writing did I realize and look through it again, that they used the 2014 api only for the extension part and not other parts, like server, database, etc.
TL;DR
So basically I needed to use the '2020-08-01-preview' api for everything besides from the extension part, where the newest api version is only '2014-04-01-preview'
I was able to deploy most of your template and use similar parameters in my own subscription. I saw in your screen capture that you are using a Free Trial subscription. I am curious if that has anything to do with the 'BadRequest' due to any sort of DTU limitation.
Here is my deployment, which failed as expected when it tried to import the databases.
I'm creating a V2 Function App and want to use Swagger/Open API for docs, however it is not yet supported in the Azure Portal for V2 Functions.
Any suggestions on how I can use Swagger with V2 Functions in VSTS to create the docs on each build?
TL;DR - Use the NuGet package to render Open API document and Swagger UI through Azure Functions.
UPDATE (2021-06-04)
Microsoft recently announced the OpenAPI support on Azure Functions during the //Build event.
The Aliencube extension has now been archived and no longer supported. Please use this official extension.
As of today, it's in preview. Although it's in preview, it has more features than the Aliencube one.
Acknowledgement 2: I am still maintaining the official one.
Microsoft hasn’t officially started supporting Open API (or Swagger) yet. But there is a community-driven NuGet package currently available:
Nuget > Aliencube.AzureFunctions.Extensions.OpenApi
And here’s the blog post for it:
Introducing Swagger UI on Azure Functions
Basically its usage is similar to Swashbuckle — using decorators. And it supports both Azure Functions V1 and V2.
Acknowledgement 1: I am the owner of the NuGet package.
For anyone looking into this, Microsoft still hasn't added Open API support for Azure Functions +v2 and there hasn't been any major movement toward it.
I faced this same issue recently and I found a pretty good solution.
If you aren't aware yet, check this out: https://github.com/RicoSuter/NSwag
NSwag is a toolchain that integrates with .NET to produce the Open API documentation and UI, but also generates the respective API clients for you.
I've used this tool for the past 2 years when working with Angular and .NET apps, it saves a lot of time and seamlessly integrates with my whole development workflow.
For Azure Functions +v2, a contributor created a generator that in less than 10 lines of code, allow us to expose the Swagger endpoint for an Azure Function class:
https://github.com/Jusas/NSwag.AzureFunctionsV2
Now, if you design HTTP-Triggered Functions using DI, grouping related operations under the same class and leveraging model binding, you might not even need to apply any custom decorator, it just works!
Here's an example of how one real API would look like:
(ignore the base class. It is part of a personal pattern I follow, unrelated to Swagger)
And this is how it looks like using a swagger UI:
There is official library Azure Functions OpenAPI Extension. It is still in preview, but looks great.
Can you drop your V2 Function to run on v1 of the runtime by starting over with a blank function app first?
The MSDN documents for Create an OpenAPI definition for a function (with a date of 11/2018 interestingly enough) example states:
By default, the function app you create uses version 2.x of the
runtime. You must set the runtime version back to 1.x before you
create your function.
But one can't just move the setting to 1:
To pin your function app to the version 1.x runtime, choose ~1 under
Runtime version. This switch is disabled when you have functions in
your app.
Which implies one must create the Function app, publish/create it, set it to V1 and then put in a function before adding a function app.
After upgrading the existing v9 site to Kentico 10 I'm getting a security exception error when loading the site. The CMS admin however loads fine. I already added the FULL trust setting in web.config but it did not work. Any idea?
Problem, based on part that I can see and exception type would be in new SQL parser which was added in one of the hotfixes for v9 and thus it is part of v10.
You seem to be using one of the properties in a web part and than passing incomplete query via ##WHERE## macro. If a where condition is like {%CurrentDocument.DocumentID%} it is not a valid WHERE and whole property has to be complete SQL statement on its own, so it could be like DocumentID = {%CurrentDocument.DocumentID%}.
You can find a bit more in this thread:
https://devnet.kentico.com/questions/invalid-sql-query-error-on-a-page
Try load the template in the Admin UI pages application, then check the event log application, you should see the detail information about the SQL error. Most likely you have a SQL call that is trying to get some data from a column that's no longer there (through upgrade).
I am using CallerServices & CertificateAPIProfile from the paypal_base.jar, and I am using a bunch of SOAP methods from the paypal_stubs.jar. Getting worried about this deadline, not sure if these are affected or not.
You must fix your app before June 17th as paypal will stop to use TLS 1.0 that is the only protocol supported by that jar version.
https://www.paypal-knowledge.com/infocenter/index?page=content&widgetview=true&id=FAQ1914&viewlocale=en_US
Here you can find a replacement for that jar supplied by PayPal:
https://github.com/paypal/PayPal-Legacy-Java-SDK
I am implementing a release mechanism for my application and want to couple it with my YouTrack using the REST API.
Upon the release I want to set the default value of
'Fix Version' for newly created issues to the bumped version.
The Fix Version is a project's custom filed. When I query for it via REST API i get
<projectCustomField name="Fix version" type="version[1]" emptyText="Unknown" canBeEmpty="true">
<param name="bundle" value="MyProject Versions"/>
<defaultValue>2.8</defaultValue>
</projectCustomField>
The documentation mentions just the way to change the name and an unset value text. I have tried POSTing the dafaultValue and dafault parameters, but with no effect. Is it's possible at all?
I have contacted JetBrains, and apparently this functionality is, sadly, not there.