I have a worklet variable which needs to be assigned with the value from the parameter file of the workflow, is it possible to do it in informatica power centre 9.1?
Please let me know how to implement this, don’t have any ideas.
Edit the worklet and look for Variables tab. There you can manage pre-worklet and post-worklet variable assignment, as described in the documentation.
Related
I want to create my own variable and want to set my default value which should work like a built in variable in Informatica. I want to use created variable in my all workflow.
Is it possible any way ?
Thanks
You can use the same parameter file across all of your mappings (there is syntax to separate out bits which are for specific sections and those which are universal by way of the scope) see following link https://network.informatica.com/thread/27560
Hi Iam novice to Informatica, I tried to get the count of inserted rows to target to WF variable, So that I can write a condition to a link to proceed to next session.
I went through few web guides and found $PMTargetName#numAppliedRows.
But I didn't able to find this property under Built-in properties in Post session on success variable assignment.
Even I tried to assign a variable in mapping level with this property, but I am getting error like Invalid symbol reference.
$PMTargetName#numAppliedRows is NOT listed anywhere among any variables. Neither in built-in nor anywhere else. Still - you can use it. Just remember to replace the TargetName with the name of your target transformation, e.g.: if you insert data to AccountList table, you'd need to use the condition $PMAccountList#numAppliedRows. Hope this helps.
Please use this link workflow variable :-
Name: TgtSuccessRows
Desciption: Rows successfully loaded
Datatype: integer
But issue is you can not track data loaded for multiple targets.
I am developing an Informaticajob with multiple sessions in one workflow. I need to assign a variable ##AAR with following code
IIF(get_date_part(sysdate,'mm') <= 7, get_date_part(add_to_date(sysdate,'YY',-2),'YY'), get_date_part(add_to_date(sysdate,'YY',-1),'YY')
)
I am not sure how to get about it, I was thinking on creating a session that assigns the variable, then passes it to the workflow.
This session should be the first session to run in the workflow. but I don't know how to create a session that is not a mapping.
What could I do to get this done?
First, you define the variables in your workflow (Workflows -> Edit -> Variables) so the workflow knows about the variables.
Then, as first Task in your workflow, you take an "Assignment" instead of a session. That's the icon that looks like a calculator.
In the assignment, you can assign values to your variables.
Please note that the variables need to be names "$$..." not "##..."
I'm using Sitecore. I want to get the full name/description of a DMS rule in programcode by Sitecore ID, for example: "Where the DayOfWeek has a value that is equal to Tuesday".
Who knows how to do this?
Thanks a lot.
Jordy
I don't know of a simple way, but the class responsible for rendering the rule text is Sitecore.Shell.Applications.Rules.RulesRenderer in Sitecore.Client.dll.
Its constructor accepts the XML from a rules field and you call the Render method, passing in a prepared HtmlTexteWriter. It also has a bunch of fairly self-explanatory private methods like RenderRule, RenderCondition etc.
I'm sure if you decompile that class you can pick out the bits you need.
I'm taking over a project and wanted to understand if this is common practice using SOAP. The process that is currently in place I have to query all the values before I do an update cause I need to pass back all the values that are not being updated. Does this sound right?
Example Values:
fname=phill
lname=pafford
address=123 main
phone:222-555-1212
So if I just wanted to update the phone number I need to query for the record, get all the values and submit these values for an update.
Example Update Values:
fname=phill
lname=pafford
address=123 main
phone:111-555-1212
I just want to know if this is common practice or should I change the functionality of this?
This is not specific to SOAP. It may simply be how the service is designed. In general, there will be fields that can only be updated if you have the original value: you can't add one to a field unless you know the original value, for instance. The service seems to have been designed for the general case.
I don't think that it is a very "common" practice. However I've seen cases where the old values are posted together with the new values, in order to validate that noone else has updated the values in the meantime.