nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Number of Replicants

kaalraa

Hi there,

Is there any limit to the number of replicants to a DCT. As per the requirement, i need to capture at the least 750 key-value pairs.

Please provide the suggestions.

Find more posts tagged with

Comments

vpatel

Hi there,

Is there any limit to the number of replicants to a DCT. As per the requirement, i need to capture at the least 750 key-value pairs.

Please provide the suggestions.

I do not believe there is a *limit* per say. However with 750 containers you may have some usability issues + potential performance issues (depending on how many fields you end up with in each container). Something to consider while coming up with the design.

kaalraa

I do not believe there is a *limit* per say. However with 750 containers you may have some usability issues + potential performance issues (depending on how many fields you end up with in each container). Something to consider while coming up with the design.

It is only 2 fields per container and thats too text fields with maxlength of 30 chars

Jamik

It is only 2 fields per container and thats too text fields with maxlength of 30 chars

as vpatel says there isn't a limit per say (just set the max to unbounded)

that said, even though you say it's two fields per container that's still 750 containers and that much data+processing( you might think it's not much since it's just too fields but you gotta think about all the processing and data around the container of those fields as well) has the potential to be very very slow. I would definitely make sure you don't have a performance problem before implementing in production.

Migrateduser

We have 350 replicants with 6 fields in each and it takes about 30 seconds to load in FireFox 3.5 and completely crashes IE7 - this is terrible. any thoughts/ideas would be greatly appreciated, thanks!

Jamik

We have 350 replicants with 6 fields in each and it takes about 30 seconds to load in FireFox 3.5 and completely crashes IE7 - this is terrible. any thoughts/ideas would be greatly appreciated, thanks!

find out what maximum number of replicants you can have that doesn't perform horribly is, set the max to that number, split your dcr into multiple dcrs.

other option is to rethink why you're using teamsite to create a document with so many replicants instead of some other system, and/or rethink your architecture as a whole.

Qualification.jpg

nipper

Hi there,

Is there any limit to the number of replicants to a DCT. As per the requirement, i need to capture at the least 750 key-value pairs.

Please provide the suggestions.

There is a bug with IE7 that was giving JavaScript errors. A couple of threads have floated around about them. I have not found a way to fix them (except use FF and be patient), however you can help your self out. I changed the fields inside the replicant from select lists to text fields. The system handled many more plain fields.

I would also use very little FormAPI (just because I was seeing a ton of JS errors)