Book a Demo

Author Topic: Repository.Execute no longer works in JScript  (Read 887 times)

Mauricio Moya (Arquesoft)

  • EA User
  • **
  • Posts: 346
  • Karma: +8/-4
  • EA Consulting and development in Spanish
    • View Profile
    • Arquehub Azure Module
Repository.Execute no longer works in JScript
« on: August 06, 2026, 11:47:33 pm »
While testing the latest version of EA (17.2 build 1721), I noticed that JScripts that were working perfectly in previous versions are now failing on lines containing Repository.Execute("insert SQL here"). I am now getting an "Internal Error" when the script reaches that line.

Does anyone know if this command has been deprecated? Has it been replaced by something else?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13527
  • Karma: +575/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Repository.Execute no longer works in JScript
« Reply #1 on: August 10, 2026, 04:55:19 pm »
I'm guessing this is one of the "security" fixes, but I'm pretty worried about that myself.

There are quite some things that are not possible in the API without resorting to the Repository.Execute backdoor method.
If this method is indeed no longer available, that would break quite a few of my add-ins and scripts.

Geert

philchudley

  • EA User
  • **
  • Posts: 751
  • Karma: +22/-0
  • EA Consultant / Trainer - Sparx Europe
    • View Profile
Re: Repository.Execute no longer works in JScript
« Reply #2 on: August 10, 2026, 06:29:41 pm »
I agree Geert, there's a lot of scripts I have developed for clients and myself which are going to break if they upgrade to EA v 17.2

Not good  >:(

Phil
Models are great!
Correct models are even greater!

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13527
  • Karma: +575/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Repository.Execute no longer works in JScript
« Reply #3 on: August 10, 2026, 09:58:29 pm »
I've sent an email to support about this one, and the restrictions on Repository.SQLQuery (where you can't select from certain tables anymore, e.g. t_seclocks)

Hoping for an alternative

If they can't provide an alternative solution, I'm guessing I'll have to resort to a direct database connection to execute these type of queries/updates.
The upside of that would be that it would be a lot faster then going through Repository.SQLQuery
Obvious downside if that you have to manage your own database connection.

Geert