Is there any limit of replicant container/fields?

Hi,

I have a DCR which contains huge number of replicants.I am using form Apis to perform some validation and saving the dcr.Upto certain limit of replicants all is working fine.But after that if we add any new container or field , it is throwing following error.

"Save was unsuccessful. Invalid category/type null was received".

I am using "max=Unbounded" limit for container/field.

Is there any limit of replicants container/fields in Teamsite?

Please provide me any help on this.

TS Version : 7.2.1
OS : Linux
Browser : IE 8

Find more posts tagged with

Comments

nipper

The only limit is your internal resource (memory, browser, etc). I suspect the practical limits vary depending on the number and type of items. There had been issues with a lot of visualformat fields, which is why they can be loaded individually.

If you remove and readd a replicant, will it save ? Try different browsers ? Any JS errors ?

Auli2

There are no VFE fields in the replicants, just the dropdowns and the textboxes. There are more than 1500 replicants in the DCR (not for 1 item but 40-50 replicants per item)

We tried removing existing and adding the replicant again, save worked fine.
But as soon as we are adding anymore replicant to any of the item, it is throwing that error (Save was unsuccessful. Invalid category/type null was received).
We have also checked the content_center.log and error.log but nothing is coming up there.

On firefox, it is not getting saved at all, even with current no. of replicants. It is throwing following JS error on firefox which I think is not related -
Error: gBrowser.addProgressListener was called with a second argument, which is not supported. See bug 608628. Source File: chrome://browser/content/tabbrowser.xml Line: 1947

All the replicant items have max=Unbounded set as the limit.

Any pointers will be greatly appreciated.

TS Version: 7.2.1
OS : Solaris 10

Adam Stoller

To help further diagnose the issue, you need to temporarily disable your FormAPI code and see whether you run into the same problem / at the same number of replicant instances.

If you do - then it sounds like a built-in limitation that you need to contact Support about (providing them a complete example and how to reproduce)

If the problem goes away with FormAPI disabled, but returns reasonably reliably when FormAPI enabled - then it has something to do with the FormAPI code. This is generally "custom code" - so there may be something that you've done wrong or in a less-than-optimal manner that is causing the problem, or you may still be hitting some sort of built-in limitation. Unfortunately, it's a lot harder to prove that the problem is built-in when you're using FormAPI code unless you can figure out how to perform the same operation using native JavaScript code in place of FormAPI functionality.

You may also want to approach this from a different front - which is to simplify the DCT dramatically (only include simple text fields, no browser fields, etc.) and see if you can get the problem to reoccur again - and if so, does it seem to happen with the same number of replicant instances or the same number of overall total fields, or what. It's unfortunate, but the onus of proving a problem to be a bug in the product is on you, the customer / implementor. It's frustrating, but can be kind of "fun" and educational along the way... (just ask Smitty ;-))

Screen Shot 2016-05-19 at 1.25.26 PM.png

Screen Shot 2016-05-19 at 1.25.34 PM.png

Screen Shot 2016-05-18 at 3.18.37 PM.png

Vip777

Thanks a lot for your responses.

We have tried to remove form api code but still problem persists.So we broke dcr into two parts.Now we are using 2 dcr instead of one.And it solves our issue.