IssueTracker

Hello there!

If I understand this request correctly, you'd like an API to retrieve all the existing products and SKUs, like the list provided here?

Can you provide more details on the workflow you have in mind and the potential usefulness of this feature?

• What impact (in terms of costs, productivity, etc.) could this feature have?
• What workaround (if any) are you currently using?

Kind regards.

In that case, can't you update the license list programmatically when a user with a new license is imported?

Hi!

We have to make numerous calls to get this information, which counts against our quota.

Can you provide more details about this? How are you getting this information?

No because the list is stored as a custom template on our side, so we don't have the ability to change it during import.

I understand it's not feasible to update the custom template on your side during the import process?

I have reported this internally. Any public updates about this will be communicated here.

Thank you.

Hi!

If you're a reseller/distributor, this might be useful to you:

• Method: products.list
• Method: products.skus.list

I don't quite understand your use case, but it might be worth investigating the Channel Services API to see if it provides an endpoint/method which will be helpful to you.

Ok here is how it's done:

function iUseTheLibrary(){ jdbc = Jdbc function usingLibrary(arg1, arg 2, jdbc) }

and in the library function

function iAmTheLibrary(arg1, arg2, dummyJdbc){ Jdbc= dummyJdbc var conn = Jdbc.getConnection(.....) }

@trbls.com's solution worked for me for a bit. After 10 or so hours it randomly stopped working again. Then I moved everything into the same script as @magentahealth.ca suggested and again everything started working for a while. Nevertheless, after a few hours it started bringing up a different error, this time it was a "Failed to establish a database connection. Check connection string, username and password" message. Checked everything from DB firewall to punctuation and spelling in my code and saw nothing wrong. Is there a timeframe established for these errors to be fixed? Do you really need another year to fix it?

Temporary solution

Sending the Jdbc object as a parameter solves the problem for me.

//Library with connection
function madeQuery(tjdbc){
   tjdbc.getConnection(url, username, password);
}

When you use the library, we send the parameter

MyLibraryWithJDBCConnection.madeQuery(Jdbc)

Tip for Apps Script maintainers

I have reviewed the Java documentation, which I assume is running behind and the location of the Driver on the server should be declared. Very surely when using a new Script you lose the Jdbc reference and this error appears. I don't know where, but I think that in the V8 engine they should specify the driver in each new script created, something like:

Class.forName("com.mysql.jdbc.Driver")

ke...@magentahealth.ca Yeah, ever since they announced V8 was releasing that started to happen. I remember some of our scripts changing to V8 as far back as 2 years ago.

I've been using Apps Script for about 8 years now and just this weekend I decided to start implementing a real MySQL database instead of Google Sheets. I spent about 8 hours tediously working through many other bugs/issues related to Jdbc and getCloudSqlConnection() only to hit this one.

While I'd love to see this bug get fixed for the sake of everyone here already relying on Jdbc in libraries already, I'm now more hesitant to implement it myself, given that any new breaking issues that come up may take 2+ years to be fixed. :(

Hi,

This issue has been fixed. To anyone previously affected by this, can you check whether you can still reproduce this?

Kind regards.

I cannot reproduce this using the steps provided in comment #1. The library function is executed successfully.

Can you provide a minimal reproducible example?

Responding to comment #90, the issue described in comment #1 has been fixed. Can you please check whether you can still reproduce this?

I am also getting "ReferenceError: Jdbc is not defined" on a script today that has been working without changes for many months.

Edit: I had a library project with a connect(tjdbc) function that returns a Jdbc connection. In another script (many actually), I had used library.connect(Jdbc), this is where the error is returned.

Today, if I edit the library function to simply use Jdbc, instead of the passed in argument, then edit the function call to be library.connect() (without the "Jdbc"), that appears to work fine now, which I don't believe worked before.

Hi,

Are you able to reproduce this in newly created projects, or just in old ones?

I can reproduce the issue in a brand new project, using library.connect(Jdbc), using the old library.

It looks like the library function itself can now succesfully use Jdbc, instead of having to pass it in as an argument. This did not work previously, thus the workaround of passing Jdbc in as an argument. This is the optimal solution, I'd like to go through all of my scripts that use this library and remove the Jdbc argument, but I'd just worry that it will get changed back in the future...

Hi,

Just to clarify this. The issue reported in comment #1 should be fixed by now, without requiring the use of a workaround. For example, if one creates a library project with this code:

function myFunction() {
  Jdbc.newDate(1000);
}

And then call it in the main project:

function myFunction() {
  LIB.myFunction();
}

No error should be thrown.

Is anyone still getting an error when doing this?

In response to comment #110,

Are you still able to reproduce it if you follow steps provided in comment #105 (using new scripts)?

I'm closing this issue as it has been fixed.

Copying and renaming the old library shouldn't be required here. Also, passing a Jdbc parameter is not needed.

If you start encountering this again in the future, please create a new issue.

For the past 6 months or so I've continued to randomly get the "ReferenceError: Jdbc is not defined" error when using the V8 runtime.

Has anyone else been experiencing this?