Skip to main content
susbhatt
Contributor ⭐️
September 18, 2019
New Idea

Option to provide Batch size for each rule

  • September 18, 2019
  • 14 replies
  • 383 views
Hello Team,

Currenly we dont have the option to change or provide the batch size specifically for a rule to update records,

Can we have that option going for future release?

Thanks,

Sushanto

    14 replies

    dan_ahrens
    Expert ⭐️⭐️⭐️
    September 18, 2019
    Hi Sushanto, can you share a bit more around the use case that you're trying to solve for with this enhancement?

    VP of Customer Success at Forcepoint
    john_apple
    Expert ⭐️
    September 18, 2019
    I agree with this. I currently have to update 16,000+ records and running into various limitations when trying to update more than 20 records at a time. If I had the ability to set a max batch of 20 I could set it to run a few times a day and then just wait for records to complete rather than constantly having to update the rule. I don't care which of the 16000 records are updated when so any random sample is fine.

    susbhatt
    susbhattAuthor
    Contributor ⭐️
    September 24, 2019
    Hi Dan,

    Sorry for the late reply.

    We have the following use case :

    We update a lot of Post sales records which is a child of Account.

    In our SFDC space Account is one of the most complex business object with lot of business logic being developed on it.

    when we update say 12 k records of Post sales via a GS rule it fails giving CPU time limit exception. We can't lower the batch size in this scenario as we dont have that option with us. We raise a case with Gainsight and they ultimately change it for the rule.

    We saw by changing the batch size to 60 from 100 improved the performance by a big margin.

    Thus if that option can be made customizable for us, we can atleast test it before pushing such changes to production and wont have to raise GS support cases everytime.

    sai_ram
    Expert ⭐️⭐️
    September 24, 2019
    @susbhatt and @john_apple We understand your concern, the only workaround for now is to do it via a support ticket, we have a process to reduce to the batch size from the backend. May be helpful for others,so posting it here again. This batch size can be reduced for a particular action too.

    @rajesh_yaddanapalli and @indraneel_pampati could you confirm?

    susbhatt
    susbhattAuthor
    Contributor ⭐️
    September 26, 2019
    Yes @sai_ram_pulluri ,

    I know the backend option is there but wanted something on UI so that we dont have to raise a ticket and go back and forth.

    If it could be made a product feature and enabled for users to choose the value.

    We are currently doing the backend option only but a custom UI option would be really helpful as a product feature

    sai_ram
    Expert ⭐️⭐️
    September 26, 2019
    @susbhatt Got you and I have redirected this to our product team. Thanks for bringing this up.

    FYI..Just to let everyone know that there is a workaround to reduce the batch size, I did highlight the point here.

    @All, I know most of them are facing the same issue, please show your presence here so that I can raise an alarm to change the priority on road-map.

    HollySimmons
    Helper ⭐️
    January 20, 2021

    We have a rule which triggers a job in SF and if more than 5 records are sent through at once it times out, so would like to be able to only send a maximum of 5 at a time (again don’t care what order they are done in) and then the next time it runs another 5 etc etc

    sai_ram
    Expert ⭐️⭐️
    January 20, 2021

    @HollySimmons I will let you know. Thanks!

    HollySimmons
    Helper ⭐️
    January 21, 2021

    So it turns out support can only do the reduction for those on SFDC, and we’re on NXT. So we’re still stuck. 

    rakesh
    Gainsight Employee ⭐️
    Lets put your data to work!
    January 29, 2021

    @HollySimmons

    There might be some technical nuance here.

    For SFDC we have custom implementation for Load to SFDC, where batch size can be customized. For NXT, we use the bulk API by SFDC. I’ll check with the team if we can make the batch size customizable.

     

    Edit: I’ve reconfirmed with the engineering team that because we use the bulk API’s that Salesforce itself provides, we should not have any problems because Salesforce takes care of optimizations. Is anyone facing any challenges with Load to SFDC in NXT edition too?