The Base collect code is just the collect.js, this script does not collect any information. All information that is tracked is gather by the track calls. There is also a Known Issue for this behavior


You can't refer to properties dynamically like that in Apex. formSubmission.fs =formSubmissionData.get(fs); If you want to place a value in the field whose name corresponds to the content of the variable fs, you must use the put() method. formSubmission.put(fs, formSubmissionData.get(fs));


The field map from a describe is a special map that is read-only. This property is important, as describe calls are cached, so if you modified the cache, you'd get unpredictable behavior in other parts of code. The immutability of the map makes sure you don't accidentally cause side-effects elsewhere in your code. If you want to make a copy, you could: Map&...


The only practical limits to how much you can display are Heap Size and CPU Time, as I answered here. I was able to populate a Map with over one million records and Visualforce allowed the collection to render. As for your other questions, there is no real difference between storage capacity for Map vs. List, other than how much memory they consume. I would ...


While there could be multiple possible ways to achieve this, but if I had to write this, I would have used classic abstraction approach here utilizing Interfaces. In your scenario, you can have a base implementation of the WrapperClass as: public interface WrapperClass { // declare all the common attributes here // add an abstract method which ...


Despite not working as documented, you should not depend on this behavior working forever. Even though it's working now, it would surely have a significant performance penalty as compared to using more modern methods. It would be better to work on proper pagination using either an API or creative querying. For example, in Lightning, you can query 50,000 rows ...


As of now, there isn't a way to pass a list of string values and display as dynamic choices in the flow's picklist component. You can check for some alternatives in a similar question asked. (Screen Flow Picklist from Lightning Component).


You can not use fs like this dynamically in apex. formSubmission.fs =formSubmissionData.get(fs); Use formSubmission.put(fs,formSubmissionData.get(fs)).


just a change in above answer List<String> uniqueEmailIdList = new List<String>(); for (Webinar_Attendees__c aa : ld) { If(!uniqueEmailIdList.contains(aa.Login__c)){ uniqueEmailIdList.add(aa.Login__c ); WebinarAttendeesWrapperList.add(new WebinarAttendeesWrapper(aa)); ...


web is a variable of type Webinar_Attendees__c. It is not a collection, and cannot be used in an iteration. To access subquery results, you must use the relationship name given in the child query as a property on the parent. This value will be typed as a List<sObject>, where the sObject is the type of the child object. for(Voucher_Repository__c ...

Only top voted, non community-wiki answers of a minimum length are eligible