SFM should be able to handle more than 100-500 rows

SFM should be able to handle more than 100-500 rows

When the SFM is heavily loaded (lot of rows/columns), you get an undefined error because Salesforce times out when ServiceMax tries to save the data. This is becoming more and more common use case and the only work around is creating custom VF pages. Can you break the rows down into smaller chunks and send it to Salesforce?

It is forcing us to develop custom VFs

What is the underlying problem do you intend to solve with this idea?
Usability
How is the problem being addressed today, if at all?
Apex
Product Area?
Communities
What version of ServiceMax are you on?
Summer 16
11 Comments
Roast Chef
Roast Chef

Same issue is seen in our org.  Pushing record through via code on SFDC only works fine, but when doing so through SVMX SFM, the undefined error comes.  For some we've debugged we're seeing too many SOQL query error.  Because this works fine in SFDC side we are confident it is within SVMX function and not SFDC itself.

Roast Chef
Roast Chef

There are separate SOQL limits for SFDC and SVMX

(SVMX-managed-package code gets its own 100 limit, separate from any custom written triggers and classes)

will look something like below

where (default) represents SFDC + custom apex

and SVMXC represents ServiceMax managed package apex

(can also be other categories for other installed managed-packages)

*use find funtion on "Limit_Usage" in the debug files

GREATLY helps narrow down where in the code you are hitting limits

09:16:28.423 (36423647577)|LIMIT_USAGE_FOR_NS|(default)|

  Number of SOQL queries: 23 out of 100

  Number of query rows: 100 out of 50000

  Number of SOSL queries: 0 out of 20

  Number of DML statements: 0 out of 150

  Number of DML rows: 0 out of 10000

  Maximum CPU time: 17 out of 93000

  Maximum heap size: 0 out of 6000000

  Number of callouts: 0 out of 100

  Number of Email Invocations: 1 out of 10

  Number of future calls: 0 out of 50

  Number of queueable jobs added to the queue: 0 out of 50

  Number of Mobile Apex push calls: 0 out of 10

09:16:28.423 (36423647577)|LIMIT_USAGE_FOR_NS|SVMXC|

  Number of SOQL queries: 101 out of 100 ******* CLOSE TO LIMIT

  Number of query rows: 2920 out of 50000

  Number of SOSL queries: 0 out of 20

  Number of DML statements: 37 out of 150

  Number of DML rows: 102 out of 10000

  Maximum CPU time: 0 out of 93000

  Maximum heap size: 0 out of 6000000

  Number of callouts: 0 out of 100

  Number of Email Invocations: 0 out of 10

  Number of future calls: 0 out of 50

  Number of queueable jobs added to the queue: 0 out of 50

  Number of Mobile Apex push calls: 0 out of 10

Recommend logging a support case, they can point you towards certain global settings that can be modified that will help avoid SOQL limit issues!

Roast Chef
Roast Chef

Thanks Alex!  This is what our developers have done in evaluating the issue.  The problem is two-fold:  1) SVMX query on entry of SFM to populate lookups - seems to be causing SFM load issues as we have moderate sized SFMs taking 20+ seconds in Chrome.  2)  SFM save within SVMX are often failing for larger records, whereas same processing in SFDC has no issues in same execution.  In other words, users cannot process, but admin can be bypassing SFM.

Roast Chef
Roast Chef

can you send me a screenshot of the SFM? im guessing this is in relation to offline-app saving (svmx) vs browser saving (sfdc) - but both within the SFM framework?

Have been battling with SOQL issues stemming from mobile devices for a while, might be able to pass on some workarounds if applicable

Roast Chef
Roast Chef

Thank you for the offer Alex.  Our issue is with SFM online only.  For example, if we have Work Order with 100 lines, we get undefined error, but if I manually set lines via code outside the SFM there are no issues.  We do have case open on this particular issue  Ramesh Kotamareddy

Roast Chef
Roast Chef

Ah i see - yea trying to insert/update 100+line items will indeed trigger SOQL limits

(each insert/update/delete action uses 1 SOQL query each i believe)

With Apex/VF you can set batching - but i do not believe it was ever imagined by SVMX that a header would have 100+ line items attached to it

You could try to split the SFM to reduce the number of records per save - like a "Add Parts" SFM Transcation and a "Add Labor" SFM as separate transactions, and just have them show up in a single SFM View process

However, for mobile devices, if both transactions are done close enough, it will still try to sync all 100 lines at once and fail out (possibly losing ALL updated data in the process!)

Open case is good idea

But this sounds like a high-difficultly and high-risk feature to program in - would not expect out-of-box batching anytime soon :/

Roast Chef
Roast Chef

Thanks Alex - this is quite helpful.  We hit the issue online (hard block of undefined) and offline (records missing on sync).  We have started trying to work around this in-house on apex end.  Ramesh Kotamareddy

Roast Chef
Roast Chef
Customer Success Team
Customer Success Team

Chris Wada​  Added to the Varian list per meeting on 6/8

Customer Success Team
Customer Success Team

Deirdre Yee​  Can you please add Varian Medical Systems to the tags?  Thanks.