Task Entry Customization Question

I am working on a form that is calling Erp.UI.TaskEntry with the following launch options:

{
	"type": "Erp.UI.App.TaskEntry.TaskArgs,Erp.Adapters.Task",
	"options": {
		"relatedToFile": "{Task.RelatedToFile}",
		"key1": "{Task.Key1}",
		"key2": "{Task.Key2}",
		"key3": "{Task.Key3}",
		"taskSeq": "{Task.TaskSeqNum}",
		"loadMode": "Update",
		"showAsModal": false,
		"calledFromCustTrk": false,
		"contextValue": {
			"Param1": "",
			"FollowUp": false,
			"FollowUpType": "",
			"FollowUpComments": ""
		}
	}
}

and immediately navigating to the details page in update mode (bypassing the landing page). I end up at read-only screen with no values populated. I can see the that the correct values are being passed in Chrome’s developer tools, but the KeyFields are not being assigned the values I am sending. Am I using the wrong variable names in the launch options? Any thoughts would be greatly appreciated.

Thank you.

Is this JSON in your LaunchOptions of the App-Open widget? Your key fields may need to be passed in as a ValueIn object.

Something like this? (Untested)

{
    "type": "Erp.UI.App.TaskEntry.TaskArgs,Erp.Adapters.Task",
    "options": {
        "valueIn":{
            "relatedToFile": "{Task.RelatedToFile}",
            "key1": "{Task.Key1}",
            "key2": "{Task.Key2}",
            "key3": "{Task.Key3}",
            "taskSeq": "{Task.TaskSeqNum}"
        },
        "loadMode": "Update",
        "showAsModal": false,
        "calledFromCustTrk": false,
        "contextValue": {
            "Param1": "",
            "FollowUp": false,
            "FollowUpType": "",
            "FollowUpComments": ""
        }
    }
}

Andrew,
Thank you for the response. I have literally been working on this since I posted the question. About an hour ago, I decided to just delete the event and recreate it. Surprisingly, that fixed the issue. I kept reading all over the web that events can get corrupted. Apparently, a lot of users have experienced this in application studio. Thank you again for your response!

1 Like