LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: egiesen

I cant seem to get the records pin to return anything other then 0. I pass in 171 records to be updated in SFDC and I know they are getting updated as I can see the values change in Salesforce. Any ideas on how to get this to work. There Is a parameter on the Optional Tab that says "Pass Through Fields" and if I choose anything other then default it says the ID field to do an update is duplicated. See message below

ERROR: Error occurred while attempting to open output (0) : "Unable to add the field (5): "SFDCID" to the output metadata. Another field with the same name already exists on the output. cause: {2}"
Error Code: brain.node.errorOpeningOutput

I've included the nodes Im using Any ideas would be great.


node:DAta_Fields_to_be_updatedinserted_2
bretype:core::Static Data
editor:Label=DAta Fields to be updated/inserted
editor:sortkey=5798b5bb78ef561b_2
output:@40fe6c55598828e5/=
prop:StaticData=<<EOX
SFDCID,EmailEncodingKey
EOX
editor:XY=540,50
end:DAta_Fields_to_be_updatedinserted_2

node:Filter
bretype:core::Filter
editor:sortkey=57d1cc27696359cb
input:@40fd2c74167f1ca2/=^.544678123f8959c7
output:@40fd2c7420761db6/=
prop:Script=<<EOX

emit EmailEncodingKey
override emit Id as SFDCID

EOX
editor:XY=650,100
end:Filter

node:Lavastorm_Update_for_Salesforce_2
bretype:lal1::Lavastorm Update for Salesforce
editor:sortkey=5798b2957c17620f_2
input:@55af9e985a723e23/=Filter.40fd2c7420761db6
input:57d1ce4a248f077d/out1=DAta_Fields_to_be_updatedinserted_2.40fe6c555 98828e5
output:@5575671f45306f3f/=
output:@55756a83132b720f/=
prop:DataFields=SFDCID,EmailEncodingKey
prop:DataFieldsParamType=Literal
prop:IdField=SFDCID
prop:IdFieldParamType=Field
prop:Method=Upsert
prop:ObjectName=USER
prop:ObjectNameParamType=Literal
prop:PassThroughFields=All
prop:ServerUrl=https://test.salesforce.com
encrypted:simple=nFZhmIpPYl/hEcZCC8xGWN0JnUKv4HJ2QgfqE/==
prop:SfdcSecurityToken=jRguUowKhTCj9PU7tEAoyfHBZ
prop:SfdcUsername=username@test.com
editor:XY=760,60
end:Lavastorm_Update_for_Salesforce_2

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: awilliams1024

Hi,

there is an example data flow for the Salesforce nodes attached to the post for the release of LAL 6.1.40 here:

http://community.lavastorm.com/threa...-library/page6

There were also some overview decks produced for these nodes which can be found here:

Lavastorm Update for Salesforce

https://public.huddle.com/a/zMYwzG/index.html

Lavastorm Get for Salesforce

https://public.huddle.com/a/JdqDVK/index.html

Lavastorm Metadata for Salesforce

https://public.huddle.com/a/gGeKxo/index.html


Regards,
Adrian

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: egiesen

Thanks for all your help with my Lavastorm Salesforce questions. I am having another issue regarding connecting using the "Lavastorm get for Salesforce" node in the LAL libaray (the one you gave me examples on). I can get connected if I have a token for salesforce, but if I remove the token I get the below error. I asked the Salesforce admins to make sure they have the IP address of our lavastorm 6.1 machine on the trust domain. They said they do. And I believe them because if I use the way we connect in 4.6 in 6.1 it works without a token (I have cut and pasted that node at the bottom in case you wanted to see it). So I was wondering has any one successfully logged into Salesforce in a trust IP without a Token or is this perhaps a known bug?
HEre is the error message I get without a token (Add a token in and it works perfectly)

[I]ERROR: Error occurred during executing request: Invalid username, password, security token; or user locked out.
Error Code: brain.nodes.sfdc.requestError

WARN: Node reported the following messages to stderr:
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)

Error Code: brain.unhandledLogging
[/I/

Thanks for your assistance.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: awilliams1024

Hi,

I can also reproduce the issue with the 'Trusted IP' configuration using the Lavastorm Get for Salesforce node. I have raised this issue with the Engineering teams as a potential bug.

Many thanks for bringing this to our attention,
Adrian

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: egiesen

Thanks Adrian for the update. Do you know how long it will take for fix? Is there a way I can get notified?

Also, I see on the node Update for Salesforce(by the way this node also requires a token like the Get for Salesforce Node), when I do something that causes an error in Salesforce (either, update, insert or Upsert) if the record produces an error (lets say due to a duplicate value in Salesforce). The old nodes would just produce a status of failed in the records output pin and then I could gracefully handle the error. Now when I get an error using this node the whole node fails with a red X and puts the error right there (even if others works). Meaning I passed in 10 records 9 worked and 1 failed. Instead of giving me 10 records on the output and putting false in the success value, the whole node fails with an X. This is obviously hard to code for and handle gracefully. Am I doing something wrong or is this how this is designed?

Below is an example of what the error looks like on a red X. I can do other errors I just wanted to give you an example of the output


ERROR: Error occurred during executing request: duplicate FederationId
Cause record #1
Error Code: brain.nodes.sfdc.requestError

WARN: Node reported the following messages to stderr:
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)

Error Code: brain.unhandledLogging

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: awilliams1024

Hi,

The fix would need to be scheduled by our Engineering team. Yes, the Trusted IP issue also affects the Lavastorm Update for Salesforce and Lavastorm Metadata for Salesforce nodes. Updates to the library nodes are announced in this thread:

http://community.lavastorm.com/threa...-library/page6

You can use the thread tools options subscribe to the thread and receive notifications (e.g. by email) when there is a new post.

The operation of the nodes is different from the previous nodes by design. I think one approach would be to use the Do While / Do While Conditional node to execute an explicit loop to handle multiple updates.

Regards,
Adrian

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: egiesen

Im not sure you understand my problem. Its not something you can do a loop through. The node processes 10 records on the input, but if one of them throws and error in Salesforce the node will then Error with a red X and shows you the error that Salesforce returns. In past processing it would just give you in the status field you get back from saleforce in the results pin and the error and success = false. You can tell the functionality for this appears to still be there as you will have the success field and error message BUT they don't populate on an error they just populate if its success. I have attached a screen print. Seems to me this isn't correct. It should NOT mark the node with a red x and instead the node should be successful except the results pin should show the error. That is how it was in the past Saleforce nodes. IF it isn't this way there is no way to really trap for errors in Saleforce.


sfdcERror.PNG

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: awilliams1024

One solution could be include the Lavastorm Update for Salesforce node in a sub data flow and use the Execute BRX node to run the node for each update, passing in the relevant attributes as parameters for each run. The runExitCode would indicate whether the individual update attempts failed.

Alternatively, the Lavastorm Transact for Salesforce node is still included in the current product and operates the same as in previous versions of LAE.