Custom metadata limit exceeded. Your organization has reached its custom metadata maximum limit.

[RiRiSi]

Time Warp version
Setup->Apps->Packaging->Installed Packages. What is the value in the Version Number column for the package Time Warp.
🚀 NEW RELEASE - Luyten v1.10 - Jan 2022

Describe the bug
Your request to install package "Time Warp Luyten" was unsuccessful....
Problem:

1. (Timeline_Configuration.WorkOrder_ChildWorkOrders) Custom metadata limit exceeded.
   Your organization has reached its custom metadata maximum limit.
   ...
2. (Timeline_Configuration.WorkOrder_WorkOrderLineItems) Custom metadata limit exceeded.
   Your organization has reached its custom metadata maximum limit.

I am installing in an org that has a very large managed package - Rootstock ERP. Wanted to use this component on some lightning pages. I had it installed in the past, and know that you provide many Custom metadata records to make the Salesforce objects immediately operational. Very nice! Linking accounts with contacts, opps, etc. And now it seems that you are configuring field service work orders. I don't know how many relationships you provide out of the box, but could you make some of them optional, so that it does not take so many metadata records?

To reproduce
Steps to reproduce the behavior:

1. Install the package from the app exchange.
2. Select all users.
3. Wait for the nasty email to come.

Email message:
Your request to install package "Time Warp Luyten" was unsuccessful. None of the data or setup information in your salesforce.com organization was affected.

If your install continues to fail, contact Salesforce CRM Support through your normal channels and provide the following information.

Organization: Rootstock RSF-DEMO (00D46000000qc5P)
User: Rilene Simpson (00546000000MLad)
Package: Time Warp (04t2w000009Bbjo)

Problem:

1. (Timeline_Configuration.WorkOrder_ChildWorkOrders) Custom metadata limit exceeded.
   Your organization has reached its custom metadata maximum limit.

2. (Timeline_Configuration.WorkOrder_Events) Custom metadata limit exceeded.
   Your organization has reached its custom metadata maximum limit.

3. (Timeline_Configuration.WorkOrder_Files) Custom metadata limit exceeded.
   Your organization has reached its custom metadata maximum limit.

4. (Timeline_Configuration.WorkOrder_ServiceAppointments) Custom metadata limit exceeded.
   Your organization has reached its custom metadata maximum limit.

5. (Timeline_Configuration.WorkOrder_Tasks) Custom metadata limit exceeded.
   Your organization has reached its custom metadata maximum limit.

6. (Timeline_Configuration.WorkOrder_WorkOrderLineItems) Custom metadata limit exceeded.
   Your organization has reached its custom metadata maximum limit.

Expected behaviour
A seamless and successful install.

Screenshots
NA

Desktop (please complete the following information) NA:

• OS: Windows
• Browser Chrome
• Version [e.g. 22]

Additional context
None

[github-actions]

Hello @RiRiSi , thank you for submitting an issue we appreciate your time. We will take a look and give you an update as soon as we can. We aim for a 72 hour response time.

[deejay-hub]

Hi @RiRiSi. We appreciate your frustration here. The limit of 10,000,000 characters and # of types is a hard limit that Salesforce imposes. We have tried to limit our impact.

Time Warp uses 1 of 200 custom metadata types allowed and uses around 2% of an Orgs allowance on the number of characters allowed

It's hard to get leaner than that!

So in short it's not really a defect with Time Warp but more a reflection on the fact that you are already using 98% of your Orgs limit. As we see it your options would be

1. Fork the repo and remove metadata type records you don't need then package your own version - this is a temporary workaround since the next package you install that uses metadata types will encounter the same issue affecting your ability to meet future requirements
2. Remove some existing metadata types that aren't needed that make up 98% of your limit currently - a better, longer term solution to make sure you have capacity to meet future requirements
3. Wait for Salesforce to increase the limit - which might never happen - you can upvote the idea to double the number of chars here -> https://ideas.salesforce.com/s/idea/a0B8W00000GdaVPUAZ/custom-metadata-size-needs-to-increase-to-20-mb

How many characters are you using currently?

[RiRiSi]

Hi, Dave Does time work only when you use Salesforce objects as the Parent Object? It seems to work fine for Accounts, Cases, Contacts. But we have our own objects that may not be related to those. For instance, production work orders. (Not to be confused with FS work orders.) Our namespace is rstk. ***@***.*** All of our custom objects and their fields are prefaced with that rstk__ also. See below: ***@***.*** ***@***.*** This didn’t work: ***@***.*** This didn’t work: ***@***.*** Best regards, Rilene [Rootstock Cloud ERP]<https://www.rootstock.com/> rilene simpSON Senior Solution Architect Rootstock Cloud ERP * ***@***.******@***.***> [Follow us on Twitter]<https://twitter.com/rootstockmfg> [Like us on Facebook] <https://www.facebook.com/RootstockSoftware> [Follow us on LinkedIn] <https://www.linkedin.com/company/rootstock-software> [Visit Rootstock online] <https://www.rootstock.com/> [Graphical user interface Description automatically generated with low confidence]<https://learningcenter.rootstock.com/> From: Dave Norris ***@***.***> Sent: Saturday, May 28, 2022 5:03 AM To: deejay-hub/timeline-lwc ***@***.***> Cc: Rilene Simpson ***@***.***>; Mention ***@***.***> Subject: Re: [deejay-hub/timeline-lwc] Custom metadata limit exceeded. Your organization has reached its custom metadata maximum limit. (Issue #188) Hi @RiRiSi<https://github.com/RiRiSi>. We appreciate your frustration here. The limit of 10,000,000 characters and # of objects is a hard limit that Salesforce imposes. We have tried to limit our impact. Time Warp uses 1 of 200 custom metadata types allowed and uses around 2% of an Orgs allowance on the number of characters allowed [image]<https://user-images.githubusercontent.com/7021883/170824200-d346b5f5-0d87-493b-9dc4-1bf26715dd47.png> It's hard to get leaner than that! So in short it's not really a defect with Time Warp but more a reflection on the fact that you are already using 98% of your Orgs limit. As we see it your options would be 1. Fork the repo and remove metadata type records you don't need - this is a temporary workaround since the next package you install that uses metadata types will encounter the same issue affecting your ability to meet future requirements 2. Remove some existing metadata types that aren't needed that make up 98% of your limit currently - a better, longer term solution to make sure you have capacity to meet future requirements — Reply to this email directly, view it on GitHub<#188 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZL3IMQLZ47TO6HINTDTEXDVMIDRBANCNFSM5XF3ZG2Q>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

[deejay-hub]

Hi @RiRiSi , custom objects and custom objects in packages should be fine. Everything you need should be in the config guide linked on the AppExchange listing. See Plot Objects in Managed Packages for examples. https://quip.com/ahFCA9VBEKtr

[deejay-hub]

Also take a look here for a similar discussion #166

[deejay-hub]

Closing since not a defect. Any follow ups can be taken to 'Discussions'

[RiRiSi]

Thanks for your response. I went through all the packages I have installed, and found one that had hundreds of lines. It’s the graphics pack, from Salesforce Labs. I have uninstalled it, and now time warp has installed. Thanks again for your help. Although, I don’t know what “Fork the repo” means. Best regards, Rilene [Rootstock Cloud ERP]<https://www.rootstock.com/> rilene simpSON Senior Solution Architect Rootstock Cloud ERP * ***@***.******@***.***> [Follow us on Twitter]<https://twitter.com/rootstockmfg> [Like us on Facebook] <https://www.facebook.com/RootstockSoftware> [Follow us on LinkedIn] <https://www.linkedin.com/company/rootstock-software> [Visit Rootstock online] <https://www.rootstock.com/> [Graphical user interface Description automatically generated with low confidence]<https://learningcenter.rootstock.com/> From: Dave Norris ***@***.***> Sent: Saturday, May 28, 2022 5:03 AM To: deejay-hub/timeline-lwc ***@***.***> Cc: Rilene Simpson ***@***.***>; Mention ***@***.***> Subject: Re: [deejay-hub/timeline-lwc] Custom metadata limit exceeded. Your organization has reached its custom metadata maximum limit. (Issue #188) Hi @RiRiSi<https://github.com/RiRiSi>. We appreciate your frustration here. The limit of 10,000,000 characters and # of objects is a hard limit that Salesforce imposes. We have tried to limit our impact. Time Warp uses 1 of 200 custom metadata types allowed and uses around 2% of an Orgs allowance on the number of characters allowed [image]<https://user-images.githubusercontent.com/7021883/170824200-d346b5f5-0d87-493b-9dc4-1bf26715dd47.png> It's hard to get leaner than that! So in short it's not really a defect with Time Warp but more a reflection on the fact that you are already using 98% of your Orgs limit. As we see it your options would be 1. Fork the repo and remove metadata type records you don't need - this is a temporary workaround since the next package you install that uses metadata types will encounter the same issue affecting your ability to meet future requirements 2. Remove some existing metadata types that aren't needed that make up 98% of your limit currently - a better, longer term solution to make sure you have capacity to meet future requirements — Reply to this email directly, view it on GitHub<#188 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZL3IMQLZ47TO6HINTDTEXDVMIDRBANCNFSM5XF3ZG2Q>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.