Emanuel V
02/13/2025, 1:07 AMMartin
02/13/2025, 1:09 AMEmanuel V
02/13/2025, 1:19 AMMartin
02/13/2025, 1:22 AMMartin
02/13/2025, 1:22 AMMartin
02/13/2025, 1:22 AMEmanuel V
02/13/2025, 1:52 AMSteve Goldberg
02/13/2025, 11:33 AMSteve Goldberg
02/13/2025, 11:33 AMEmanuel V
02/19/2025, 1:47 AMEmanuel V
02/25/2025, 5:39 AMSteve Goldberg
02/25/2025, 11:02 AMEmanuel V
02/25/2025, 1:14 PMSteve Goldberg
02/25/2025, 1:27 PMEmanuel V
02/25/2025, 11:26 PM"name": "MyHeaderCustomisation",
"fantasyName": "My Header Customisation",
"vendor": "Acme",
"type": "extension",
"target": "SCS",
"target_version": {
"SCS": ">=24.2.50"
},
"version": "1.0.0",
"description": "Logo and navigation customisations",
Steve Goldberg
02/26/2025, 10:57 AM"target_version": {
"SCS": ">=24.2.50"
}
So this is your problem. You are targeting an incorrect version.
Target version is of the product itself - SCS means "SuiteCommerce (Standard)" and the version after is the version of SCS that you are targeting, which is 24.2.50. Which doesn't exist. Therefore, it won't show.
You can be much more liberal with your version targeting when writing something for SC because sites are constantly updated. In fact, you really only need to set a specific value if you are aware of a specific limitation that in your extension that is not backwards compatible (eg an extensibility method that was introduced in a specific version).
For you, I would just set this ">=18.2.0" and try again.Emanuel V
02/27/2025, 12:07 PM