cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
Read only

Custom Extension in an MDK App (Using Metadata Approach)

a_kingston
Explorer
0 Likes
586

Hello Experts,
I am trying to create a custom extension for SSAM 2310. I followed this  Create Extension Controls  documentation, but I encountered a problem. My workspace contains two projects: one is the standard SSAM 2310 metadata, and the other is ZComponent(ZSSAM2310), where I have made all the modifications.

I created my custom extension within the ZComponent(ZSSAM2310) project. However, I am getting a 'Failed to find module' error with the specific extension location.

How can I resolve this issue? Could you please provide some insights or suggestions on how to create and access the extension from ZComponent in my SSAM application?

a_kingston_0-1735550874239.png

a_kingston_1-1735550975887.png

SAP HANA service for SAP BTP  , SAP Field Service Management, connector for SAP Business One  
#SAP Service and Asset Manager,   #SAP Mobile Services,  #SAP Mobile Asset Management , SAP BTP, Kyma runtime  , SAP HANA Enterprise Cloud 

Thank you very much in advance,
Kingston. A

Accepted Solutions (0)

Answers (1)

Answers (1)

muhammad_rafay
Product and Topic Expert
Product and Topic Expert

Are you creating a custom extension using metadata or building a native extension? How are you using the extension in the metadata? The error shown in the screenshot is trying to find the extension under the extensions/ folder, which is where all the native script plugin are based.

a_kingston
Explorer
0 Likes

Hi @muhammad_rafay 

Thank you for your response. I followed the documentation Create a Slider Custom Control in an MDK App (Using Metadata Approach) to use the Slider Custom Control in my SSAM2310 application. However, if I only register the extension under my Component project (ZSSAM2310), it doesn't work, and it shows the error: "Failed to find module."

But, when I register the same extension control in the standard application and map the Extensions .TS file in the CIM file, it works fine.

a_kingston
Explorer
0 Likes

a_kingston_0-1735879754448.png