Introducing Custom Metadata property through a package

Hi,
I want to introduce a new custom metadata property for my assets which could be displayed in the DAM metadata UI of an asset as below. I can see some steps mentioned to do this in http://dev.day.com/docs/en/cq/current/dam/how_to_edit_metadata.html. However I want to do this through a package that I am developing. Hence whenever my package is installed in CQ some custome metadata properties must be automatically regisitered for all assets.
To summarize I have following queries:
How to create/register custome metadata proerties for assets in a package using CQ APIs ?
Once a custome metadata prperty is registered how to update its value using Asset API ?
Appreciate any help here!

Check http://www.wemblog.com/2013/01/how-to-associate-cug-with-dam-asset-in.html is that helps.
Yogesh

Similar Messages

Editing and sharing custom metadata/keywords through Adobe Drive in Adobe Bridge

I am part of a four-person video production unit operating within a local governmental entity. We are currently using four licenses of Adobe Master Collection CS5, and are about to get access to dedicated SAN storage.
We would like each user to have the ability to assign specific keywords to any given video clip (or remove keywords from clips) within Adobe Bridge, and have the three other users see the same results. I've noticed that Bridge alone will allow for keywords to be added or removed, but this list is specific to each user. Importing one list into other users' profiles is a start, but would no longer work, once keywords are added or taken away.
The overview page for Adobe Drive 3 says that it, "allows users to edit and view custom metadata/properties through Adobe Drive in Adobe Bridge," but I haven't found any explanation in either the website, forums, or user's guides that delves any farther into this area. If we incorporate Adobe Drive/Bridge into our workflow, will we be able to share/sync keywords between users? Is there some other (affordable) solution that would let us do this?
Thanks for any insight you might be able to offer.
Chuck

Hi,
Thanks for sharing your case.
The keywords you mentioned is XMP metadata, if all your digital assets are managed by ADEP CQ DAM service, you can use AD3 with built-in ADEP connector to communicate with the DAM server, then, I think it can meet your requirement, it means, the keywords can be set by one user through metadata panel in Bridge, and can be viewed by other users.
for custom properites, it's different from XMP metadata, it refers to the properties of one asset which is managed by a Content Management service. users have to use another UI to edit/view them in Br after AD3 is installed.
here are some requirements to use it.
1) CMIS 1.0 compiliant server should be used to manage all your digital assets
2) use the built-in CMIS with AD3 to connect to the server.
if other kind of servers are used, you should develope a custom connector through AD SDK to enable custom properties feature as well as some other handler required by AD SDK
thanks

Rename MetaData property in KM

Hi All,
I am using a metadata property called "year" for my document repository. All the existing documents are using this property.
Now if i want to change the display name to " Calendar year" , it changes and saves.
But when i create a new document in the repository, the property vanishes.All other properties are there. Now when i rename it back to "year" , it appears again.
Any idea how to rename an existing metadata property , which is being used in repository ?
Regards
PN

HI ,
Is it possible to change the label directly for the Meta data property created in the "properties " of the metadata since the display name is actually the name which i enter for the property?
I see the "label" field in the custom metadata property "year" which i had made .
Kindly let me know
Regards
PN
Edited by: Portal Newbie on Jul 3, 2008 5:35 AM
Edited by: Portal Newbie on Jul 3, 2008 5:36 AM

XML form and metadata property of a resource

Hi,
Is there any way to set custom metadata property of KM resource by entering it into input field of XML form?
Can we relate property of a KM resource to the field created in XML form?

Hi Deepti,
check out the last reply in this <a href="https://forums.sdn.sap.com/thread.jspa?threadID=9449">thread</a>. It tells you how to work with predefined property meta data in the XML forms builder.
Hope this answers your question,
Robert

Multiselect Metadata Property in XML Form

I have created an xml form to create news items for our company. The basics of the form can be found on http://service.sap.com/nw-howtoguides at Portal>KM and Collaboration>KM. I would like to add a custom metadata property that i have created that is multiselect. However i can't seem to figure out how to add the multiple checkboxes.
Anyhelp would be appreciated.

Hi Carsten,
I think you might be able to help me out in this.
I have created a multi valued property named sls_region with allowed values All, America, Europe. I have assigned this property in custom parameter section of Editxsl file of xml form.
I have created a filter with sls_region property with all allowed values for property available in dropdown.
While uploading news whatever value is selected in dropdown of filter gets assigned to custom property of the form.
To make it more clear
sls_region has value All, America, Europe
If in filter dropdown America is selected ..custom property has value set as America
If in filter dropdown Europe is selected ..Custom property has value set as Europe
If in filter dropdown All is selected ..Custom property has value set as All
This is working fine .Code which I am using for this is
<xsl:param name="ext_mars:sls_region" />(Defined in custom parameters section)
<input size="30" type="hidden">
<xsl:attribute name="name">wcmprop.mars:sls_region</xsl:attribute>
<xsl:if test="$ext_mars:sls_region=' '">
               <xsl:attribute name="value" /> </xsl:attribute>
          </xsl:if>
             <xsl:if test="$ext_mars:sls_region!=' '">
               <xsl:attribute name="value">
<xsl:value-of select="$ext_mars:sls_region"/></xsl:attribute>
          </xsl:if>
</input>
But I need to change functionality like when user select All in dropdown of filter, all available values for that custom property get sets in form.
If in filter dropdown All is selected ..Custom property should have value set as All, America, Europe
Please guide me how to modify above code to achieve this.
Regards,
Madhvika

Custom metadata fields?

I'm trying to find a way to create custom metadata fields so I can better organize my footage. For example, say I'm filming a bunch of old cars, and I want to sort them by make and model, obviously there's no make and model field by default. I've read articles that say this is possible, but I can't seem to find a way to do it. Thanks!
Edit: And related to that, is there a way to delete any of the metadata fields? Since I'm doing video, I'd rather not have to scroll through things like Album and Artist, etc. Thanks.

In the Metadata panel open the flyout menu in the upper right and choose "Metadata Display..."
Now you can turn off the metadata schemas you're not interested in seeing.
Now click the New Schema button.
Give your new Schema a name.
Now click the Add Property button next to your new custom schema.
Give it a name, like "Make", of type "Text".
Then do the same again for "Model".
Now you can select a set of clips all of the same make then enter what you'd like into the "Make" field and that metadata will be applied to the selected clips.
This is searchable, so in the Project panel you can search for the text you've entered into one of these fields and only clips containing that metadata will appear in the list (next to the search box Prelude reports "(filtered)" to let you know you're not currently seeing all of your clips.
I hope this helps!

Custom Metadata Panels from CS3 to CS4.

I have install CS4 on my Vista Ultimate PC. It runs like a dream. However there is now a new format for the custom metadata panels. I have two panels that I created in CS3 that I need to convert to the new format. Is there an easy way to do this?
The CS3 files are txt files that all I had to do was copy to the proper directory and they appeared. Thanks.
Fred

Thanks Gunar,
I already had my custom XMP panel for my server product for InDesign. I tried to create a CS4 compatible panel on MacPro (Mac OS X 10.5.5 3GB RAM) using every possible method from the XMP FileInfo SDK pdf - it didn't work. The panel did show up in the dialog, but not the fields. Not only this, all fields also disappeared from some other panels. After I removed my custom panel, everything went back to normal.
I tried:
-Generic panel method - the fields didn't show up
-The Flex SDK method: when I run
ant built.xml
I got the "Target "build.xml" does not exist in the project "TestPanel"." error (I checked many times - all the files were where they're supposed to be, and I run it from the correct directory).
-I downloaded Flex Builder, followed all the steps - the fields didn't show up, and fields in other panels disappeared.
The idea of building the panel interface interactively is great - I hope it will ever work.
Any ideas of why it didn't work for me?
While we're on this, I think that the new tabbed interface for the File Info dialog is a huge step back. You already had a great interface, with the list of panel names on the left side - which is easy to use and is standard through many Adobe dialogs.
The multi-tab approach for many items proved to be inefficient long time ago. Right now you created a dialog that works like a dilaog in QuarkXPress 4 - what's the point?
To support the new tabbed interface, you had to introduce TWO new "arrow" controls, none of which is user-friendly, and which make a simple task of choosing a panel extremely confusing.
The new feature of changing panel position by dragging is great, but it could be also achieved through the side list approach.
Bottom line: could you please restore the side list approach. I think it will help advance the XMP technology further and encourage people to actually use it , instead of doing exactly the opposite.
Best,
Leo Revzin
Zevrix Solutions
zevrix.com

Setting the custom master page through powershell is NOT working

Hi,
I am writing the below code to set the custom master page through powershell.
But its not working .when i went to site settings-->master page --> in the drodown , the maste page set is seattle.master ONLY, though my current master page is available in the dropdown.
Can anyone pls help, whether i am missing in the below :
      Add-PSSnapin Microsoft.SharePoint.Powershell
       $SiteURL = "http://srvr1:22307/sites/SPW5"
    $weburl= $SiteURL
    $Site= Get-SPSite $SiteURL
    $web = $Site.OpenWeb()
$web.CustomMasterUrl = "/_catalogs/masterpage/myMasterpage.master"
$web.MasterUrl = "/_catalogs/masterpage/myMasterpage.master"
$web.Update()
Das

Hi,
Is it a publishing page? If yes can you try the PowerShell scripts corresponding to the following code snippet?
var publishingWeb = PublishingWeb.GetPublishingWeb(web);
publishingWeb.CustomMasterUrl.SetInherit(inheritFromParent, false);
publishingWeb.CustomMasterUrl.SetValue(masterPageUrl, false);
publishingWeb.MasterUrl.SetInherit(inheritFromParent, false);
publishingWeb.MasterUrl.SetValue(masterPageUrl, false);
I've noticed sometime (not sure though) that Master page doesn't get updated if the inherit property is not updated first.
Thanks,
Sohel Rana
http://ranaictiu-technicalblog.blogspot.com

Custom Metadata for Microsoft Word

Since Microsoft Word has a limited property/metadata fields and there is no budget to purchase a document management system, I am thinking of storing custom metadata fields in a XML file or a database.
Can Ultra Search be configured to search the Word documents by full-text and metadata fields? If so, how?

You should start by downloading the Acrobat SDK and building the sample plugins. This is C/C++, there is no support for .NET.
Next you will need to read the relevant section of ISO 32000-1:2008 (the PDF standard) or a book such as “Developing with PDF” (from O’Reilly). This is required to understand how the PDF file format and objects work.
Finally, you can then start looking at the SDK documentation around the Cos and PD layers to apply to what you need to do.

Adobe CQ5.5 Digital Asset - Delete default metadata and how to create custom metadata

Hi
I am trying to create custom metadata for all format of assets (PDF, DOC, TXT, etc.,). I have created the dam folder under apps node as below:-
Step 1: /apps/dam/content/asseteditors/formitems
Step 2: Included the four property as textfield and selection according to our requirement under formitems
Step 3: I changed the cq:allowedTemplates from /content/dam/jcr:content
Step 4: I tried to upload the asset, I could get the custom metadata for Txt, Doc, PPT, XLSX
Step 5: But for JPG, PNG and PDF I am getting the default metadata which is huge list.
How to control this one? I want my custom metadata only displayed for creation assets. Find the attached.
CRX - Custom Template Configured
CRX - Custom Metadata populated for ZIP format
CRX - Custom Metadata not populated for PDF format

Hi,
If you read the description under section http://dev.day.com/docs/en/cq/current/dam/how_to_edit_metadata.html#Creating New Metadata Property for Assets you will find yout the format for images and its different format stores at different location. So to deal with image metadata plz try below
1. Create a "image" node under "/apps/dam/content/asseteditors" as sling folder and configure it similar to "/apps/dam/content/asseteditors"
2. under this folder again copy paste the "/libs/dam/content/asseteditors/formitems" and customize it accordingly
Above will help you to manage with all types of images. Now if you want to have separate group of property for different image types then similar to above you have to create format node inside image folder for example jpg file type create a node with name "jpeg" under "image" node & configure similarly as you did for image.
I hope it will help you to proceed. Please let me know for more information.
Thanks,
Pawan

How To Set Custom Metadata Programmatically?

I could have sworn there was a way, but I sure can't figure it out right now - anybody know if or how?
PS - I thought at first catalog:setPropertyForPlugin would do it, but it seems to just set some invisible property, not the viewable, filterable, custom metadata kind.
Thanks,
Rob

To build on John's reply, double-check that the metadata definition declares the field browsable and searchable, e.g.
    metadataFieldsForPhotos = {
        {id = 'type',
         title = "Type",
         dataType = 'string',
         browsable = true,
         searchable = true},

How to hide custom metadata field in custom profies ??

hi,
how to hide custom metadata dropdown list in a custom profile based on choosing the security group.
ex: if i choose xxx security group, custom metadata dropdown should not appeared, for remaining security groups it should be visible.
so, Based on criteria, custom metadata should be hidden in custom profiles..
how to achieve it ?? where and how to configure ??
Detail guidance should be required
Thanks in advance

You cannot do this through profiles alone if I understand you correctly.
If I load a check in page, choose a security group and at this moment want a custom metadata field to disappear then you are beyond what profiles offers.
Rules evaluation can only be based on information that is know at the time the page is requested. That means in order for this to work you would need to make security group an non editable field and have a set of profiles for each security group.
The alternative is to customize the UI with soem DHTML or AJAX
Tim

How to use ADD_METADEF to add a custom metadata field

Hi All,
I am trying to add a custom metadata field to check in profile, and this I want to do using RIDC library through my java program. I have tried the following code, but some how I could not see its getting added to Information Fields and also to Standard check in profile.
Can you let me know what am I missing?
            myIdcClient = myIdcClientManager.createClient("idc://XXXX:4444"); // just commented out
            IdcContext myIdcContext = new IdcContext("weblogic", "weblogic1");
            ServiceResponse myServiceResponse = null;
              DataBinder myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "UPDATE_OPTION_LIST");
                myRequestDataBinder.putLocal("dKey", "xLocationList123");
              myRequestDataBinder.putLocal("OptionListString", "Madrid\nTokyo\nLondon\nWashington");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "ADD_METADEF");
                myRequestDataBinder.putLocal("dName", "xLocations123123");
                myRequestDataBinder.putLocal("dIsRequired", "0");
                myRequestDataBinder.putLocal("dOptionListKey", "xLocationList123");
                myRequestDataBinder.putLocal("dOptionListType", "choice");
                myRequestDataBinder.putLocal("dIsOptionList", "1");
                myRequestDataBinder.putLocal("dIsSearchable", "1");
                myRequestDataBinder.putLocal("dIsEnabled", "1");
                myRequestDataBinder.putLocal("dType", "Text");
                myRequestDataBinder.putLocal("FieldName", "xLocations123123");
                myRequestDataBinder.putLocal("dCaption", "Locations");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                //IdcService=UPDATE_META_TABLE
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "UPDATE_META_TABLE");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "START_SEARCH_INDEX");
                myRequestDataBinder.putLocal("IsRebuild", "1");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "PUBLISH_SCHEMA");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
Thanks in advance.

Try calling the following code:
import static intradoc.shared.MetaFieldUtils.hasDocMetaDef;
import static intradoc.shared.MetaFieldUtils.updateMetaDataFromProps;
import intradoc.common.ServiceException;
import intradoc.data.DataBinder;
import intradoc.data.DataException;
import intradoc.data.Workspace;
    protected static void addMetadataFields(final Workspace workspace, final DataBinder binder) {
        traceVerbose("Start addMetadataFields");
        // Parameters for metadata field
        final String[] parameters = new String[] { "dsdComponentName", "dComponentName", "dsdVersion", "dType", "dIsRequired", "dIsEnabled", "dIsSearchable", "dIsOptionList", "dOptionListKey", "dOptionListType", "dDefaultValue", "dOrder", "dIsPlaceholderField", "dsdCheckFlag",
                "dsdDisableOnUninstall" };
        // Common values for primary and alternate field values
        final String[] values = new String[] { "ComponentName", ComponentName, "build_1_20131206", "BigText", "0", "1", "1", "0", "", "", "", "2500", "0", "", "" };
        // Primary file checksum field parameters and values
        final Properties field = new Properties();
        for (int i = 0; i < parameters.length; i++) {
            field.put(parameters[i], values[i]);
        // Setup primary file specific parameters
        field.put("dName", "Metadata field name");
        field.put("dCaption", "Metadata field caption");
        try {
            // Name of metadata field
            final String fieldName = field.getProperty("dName");
            trace("dName: " + fieldName);
            if (fieldName != null && fieldName.length() > 0 && !hasDocMetaDef(fieldName)) {
                try {
                    updateMetaDataFromProps(workspace, null, field, fieldName, true);
                    trace("Successfully added metadata field " + fieldName);
                } catch (final ServiceException e) {
                    warn("Metadata field " + fieldName + " was not installed.", e);
                } catch (final DataException e) {
                    warn("Metadata field " + fieldName + " was not installed.", e);
            } else {
                trace("Metadata field already exists; will not modify");
        } finally {
            traceVerbose("End addMetadataFields");
Jonathan
http://jonathanhult.com

UCM Query, sort by custom metadata

Hello
I read Yannick's post about Using CMIS query in Content Query navigation model, but I have a question about sorting:
I have a custom metadata field called xEventStartDate - I want to sort my results by this metadata field.
My CMIS query is:
select * from ora:t:IDC:GlobalProfile WHERE IN_TREE('/AcqUCM/IDC:Folder/133054394311000404') ORDER BY ora:p:xEventStartDate ASC
The error I get back is:
<VcrExpressionSearchDelegate> <getPropertyDefinition> No such property ora:p:xEventStartDate for type ora:t:IDC:GlobalProfile(IDC:GlobalProfile).
<QueryRetrieverImpl> <getNodes()> Error retrieving node(s).
oracle.webcenter.doclib.internal.model.presenter.PresenterRetrievalException: Sep 28, 2011 2:32:30 PM oracle.webcenter.doclib.internal.model.presenter.PresenterRetrievalException asError
ALL: Error retrieving node(s).
     at oracle.webcenter.doclib.internal.model.presenter.PresenterRetrievalException.asError(PresenterRetrievalException.java:55)
     at oracle.webcenter.doclib.internal.model.presenter.vcr.QueryRetrieverImpl.getNodes(QueryRetrieverImpl.java:69)
Caused by: oracle.webcenter.doclib.internal.model.presenter.conf.PresenterConfigurationException: oracle.webcenter.content.integration.cmis.query.ParseException: Sep 28, 2011 2:32:30 PM oracle.webcenter.content.integration.cmis.query.VcrExpressionSearchDelegate getPropertyDefinition
SEVERE: No such property ora:p:xEventStartDate for type ora:t:IDC:GlobalProfile(IDC:GlobalProfile).
     at oracle.webcenter.doclib.internal.model.presenter.conf.QueryStringDatasource.toSearch(QueryStringDatasource.java:113)
     at oracle.webcenter.doclib.internal.model.presenter.vcr.QueryRetrieverImpl.getNodes(QueryRetrieverImpl.java:64)
     ... 172 more
Caused by: oracle.webcenter.content.integration.cmis.query.ParseException: Sep 28, 2011 2:32:30 PM oracle.webcenter.content.integration.cmis.query.VcrExpressionSearchDelegate getPropertyDefinition
SEVERE: No such property ora:p:xEventStartDate for type ora:t:IDC:GlobalProfile(IDC:GlobalProfile).

hmmm
that doesn't work... i got the following error:
<QueryRetrieverImpl> <getNodes()> Error retrieving node(s).
oracle.webcenter.doclib.internal.model.presenter.PresenterRetrievalException: Oct 19, 2011 11:36:15 AM oracle.webcenter.doclib.internal.model.presenter.PresenterRetrievalException asError
ALL: Error retrieving node(s).
at oracle.webcenter.doclib.internal.model.presenter.PresenterRetrievalException.asError(PresenterRetrievalException.java:55)
     at oracle.webcenter.doclib.internal.model.presenter.vcr.QueryRetrieverImpl.getNodes(QueryRetrieverImpl.java:69)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: oracle.webcenter.doclib.internal.model.presenter.conf.PresenterConfigurationException: oracle.webcenter.content.integration.cmis.query.ParseException: Oct 19, 2011 11:36:15 AM oracle.webcenter.content.integration.cmis.converters.NameConverter getPropertyDefinitionByQueryName
SEVERE: Invalid property name ora:t:IDC:GlobalProfile:xEventStartDate.
     at oracle.webcenter.doclib.internal.model.presenter.conf.QueryStringDatasource.toSearch(QueryStringDatasource.java:113)
     at oracle.webcenter.doclib.internal.model.presenter.vcr.QueryRetrieverImpl.getNodes(QueryRetrieverImpl.java:64)
     ... 208 more
Caused by: oracle.webcenter.content.integration.cmis.query.ParseException: Oct 19, 2011 11:36:15 AM oracle.webcenter.content.integration.cmis.converters.NameConverter getPropertyDefinitionByQueryName
SEVERE: Invalid property name ora:t:IDC:GlobalProfile:xEventStartDate.

Metadata property as Details Property in Details Screen

Hi,
is there any way (java class) to display a metadata property as a details property in a details screen (I think the default details area is overview_description).
Thanks in advance.
Regards
Ray

Hi,
you can create a class that extends AbstractResourceDetailsProperties and renders a metadata property, similiar to the standard ModifiedDetailsProperty, for example, that renders the Modified Property.
For example if I have a property named Customer I would create a class called CustomerDetailsProperty something like this:
public class CustomerDetailsProperty extends AbstractResourceDetailsProperties {
     public CustomerDetailsProperty() {
     public boolean isPropertyAvailable(IResource resource) {
          com.sapportals.wcm.repository.IProperty tempProperty = null;
          try {
               if (getPropertyName() != null)
                    tempProperty = resource.getProperty(getPropertyName());
          } catch (ResourceException rEx) {
               log.errorT("Could not check property availability for resource < "
                         + resource
                         + " > "
                         + LoggingFormatter.extractCallstack(rEx));
               return false;
          return tempProperty != null;
     public Component renderDetailsProperty(IResource resource) {
          try {
               com.sapportals.wcm.repository.IProperty customerProp = null;
               com.sapportals.wcm.repository.IProperty tempProperty = null;
               if (getPropertyName() != null) {
                    tempProperty = resource.getProperty(getPropertyName());
                    customerProp =     resource.getProperty(PropertyName.getPN("http://sapportals.com/xmlns/cm", "Customer"));
               if (tempProperty != null) {
                    String header =     getPropertyLabel(tempProperty, resource.getContext());
                    GridLayout grid = new GridLayout();
                    grid.addComponent(1, 1,     renderShortDateProperty(tempProperty, resource));
                    if (customerProp != null) {
                         Component customer = PropertyRenderUtil.renderProperty(customerProp , resource,     0);
                         Link userLink = null;
                         if (customer instanceof Link) {
                              userLink = (Link) customer;
                              userLink.setLinkDesign(LinkDesign.RESULT);
                              grid.addComponent(2, 1, userLink);
                              grid.getCell(2, 1).setWidth(";padding-bottom:3px;");
                         } else {
                              grid.addComponent(2, 1, customer);
                              grid.getCell(2, 1).setWidth(";padding-bottom:3px;");
                    return render(header, grid);
               } else {
                    return null;
          } catch (WcmException wcmEx) {
               log.errorT(
                    "Could not render lock property for resource < "
                         + resource
                         + " > "
                         + LoggingFormatter.extractCallstack(wcmEx));
          return null;
     public IResourceDetailsProperty getNewInstance(int priority) {
          CustomerDetailsProperty detailsProperty = new CustomerDetailsProperty();
          detailsProperty.setPriority(priority);
          return detailsProperty;
     public IPropertyName getPropertyName() {
          try {
               return PropertyName.getPN("http://sapportals.com/xmlns/cm", "Customer");
          } catch (ResourceException e) {
               e.printStackTrace();
               return null;
     static Class _mthclass$(String x0) {
          try {
               return Class.forName(x0);
          } catch (ClassNotFoundException x1) {
               throw new NoClassDefFoundError(x1.getMessage());
     private static Location log =
          Location.getLocation((com.mycompny.CustomerDetailsProperty.class).getName());
Best regards,
Avishai Zamir

Introducing Custom Metadata property through a package

Similar Messages

Maybe you are looking for