illegal assignment from string to datetime

Error while updating fields. line 326, column, illegal assignment from String

Example of Full Error Message: Error while updating fields. Error message: line 326, column, illegal assignment from String to Datetime

How this error may happen:  This error can happen when trying to generate a document and also trying to update Date field once document generation is done.

How to resolve: If had created a formula field and tried to remove the NOW() from the code, then you also need to copy new button code to the button. If you would like to apply value to some date field, we would suggest that you update some text field and then create Workflow that would update Date field.

• Developers Forum

DateTime Assign: Cannot convert string to date time

• 1 year ago 1 March 2023

• Alessandro 3854

I have CSV file where I have a date/time field as “(1/30/2023 1:35:45 PM)”. What I want to do is figure out the Month and Year.

I am using the DateTime: Assign to convert the string into a datetime value. However, the only output I get from the bot is an unhelpful error “An exception occurred while parsing the date time”

No matter what string we enter, we get the same error. I’m not sure what we’re doing wrong. How have you made this work?

Best answer by Diksha.M1 1 March 2023, 09:41

• 786 replies

Hi @Alessandro 3854  ,

First please check what is the Date format you are getting on the System variable called Date. First assign it to a variable and display it after converting to String. You should follow the same format while assigning the Date from the CSV file and later you can choose you desired format while converting it to string.

Hi Alessandro 3854  ,

If you have the Date Time value in string format and while using DateTime: Assign to convert the string into a datetime value, Use the Custom Formats as M/d/y h:m:s a  , It will give you the datetime D1 in correct format. 

Then you can use DateTime: To String action and use the variable D1 and the custom format as y or M to get the year and month respectively. Thanks,

Thanks for the help. Unfortunately I could not get it to work. I tried the following using your feedback.

Example #1: Date Time: 1/30/2023 1:35:45 PM Custom Format: M/d/y h:m:s a

Example #2 Date Time: 1/30/2023 Custom Format: M/d/y Example #3 Date Time: 1/30/2023 Custom Format: MM/dd/yyyy

Hi  Alessandro 3854 , 

Can you share more details about the issue.

I am using similar things and its working for me fine.

This is odd. Tried it again and it worked. No change from my side.

I believe the steps outlined were correct, so I will assume this was an issue with the environment.

• 1 month ago 11 March 2024

I have CSV file where I have a date/time field as “(1/30/2023 1:35:45 PM)”. What I want to do is figure out the Month and Year How to do this Conversion...i tried with above steps mentioned but the error remains the same  dateTime' expecting 'ZonedDateTime' received 'String'

Hi @Prade 1645 ,

My solution was 1. Remove the first “(“ and last “)”. I used a replace function 2. Then use the DateTime:Assign

• Custom format
• M/d/yyyy h:mm:ss a

Already have an account? Login

Login to the Pathfinder Community

Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.

Scanning file for viruses.

Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.

This file cannot be downloaded

Sorry, our virus scanner detected that this file isn't safe to download.

Salesforce Globe For You - Salesforce Shorts

A blog containing Salesforce coding examples in detail.It's a place where you can find solutions to the problems that you may face in your daily salesforce coding. Apex classes,visual force page,we services,Integration,plugins,extensions,Lightning web components,Aura components,Email Messages,Sales cloud,service Cloud,Marketing Cloud.Lightning Web components,salesforce.com, Salesforce Tips and Tricks,short cuts,ApexMocks,Stubs, visibility,Salesforce Shorts

Search This Blog

Friday, august 31, 2018, error: compile error: illegal assignment from datetime to date, no comments:, post a comment.

• How to deploy/retrieve a visualforce page using package.xml file in salesforce Assume AccountPage is an apex class in salesforce. Sample Xml file : <?xml version="1.0" encoding="UTF-8"?> &l...

Type Casting in Apex

Hello devs,

What are Upcasting and Downcasting? How can you cast Apex Map, List, and Set? What is a supertype, and what is the difference between SObject and Object? Answers to these questions and much more can be found in this post!

Let's begin.

Before We Start

I am using different emojis to grab your attention:

• 🚨 - Unexpected casting behavior.
• ✅ - Code that works.
• ❌ - Code that does not work.

What supertype is?

A supertype is an abstract/virtual class or an interface that is used by a child class.

The Parent interface is a supertype for the Child class.

A class can implements many interfaces, meaning that a class can have many supertypes .

The Parent abstract class is a supertype/superclass for the Child class.

A class can extends only one abstract class, but it can still implements many interfaces.

The Parent virtual class is a supertype/superclass for the Child class.

A class can extends only one virtual class, but it can still implements many interfaces.

Upcasting vs Downcasting

You know what supertype is, it's necessary to understand the difference between Upcasting and Downcasting .

To better understand upcasting and downcasting, we need some examples.

We have two classes (it can be also class and interface), Parent and Child .

• Parent is a virtual class and has a virtual method.
• Child extends the Parent class and override the virtual method.

If you don't understand what virtual means, you can refer to the Abstract, Virtual, Interface in Apex post.

• Child extends the Parent class. It means that Parent is a supertype/superclass for Child . Because of this, the following syntax: Parent parent = new Child(); is valid.
• Casting a subclass ( Child ) to a supertype/superclass ( Parent ) is called Upcasting .
• Upcasting can be either explicit or implicit.

Implicit Upcasting

Upcasting can be done implicitly.

Explicit Upcasting

Code should be as simple as possible (KISS rule), so the better approach is to use implicit upcasting.

The parent variable has access to:

• Parent public variables.
• Parent public methods.
• Child ONLY overriden methods.

Downcasting

• Casting a supertype/superclass ( Parent ) to a subclass ( Child ) is called Downcasting .
• Upcasting can be done ONLY explicitly.

Implicit Downcasting

Downcasting CANNOT be implicit. Why?

• There can be many children of the Parent class. e.g public class Child2 extends Parent { ... } .
• Apex needs to know to what type the variable should be cast to.

Explicit Downcasting

You have to cast explicitly (Child) so the compiler checks in the background if this type of casting is possible or not. If not, you will get System.TypeException: Invalid conversion from runtime type Parent to Child .

The child variable has access to:

• Child ALL public methods and variables.
• SObject Class

SObject is a supertype for:

• all standard objects (Account, Contact, etc.)
• all custom objects (MyCustomObject__c)

Object is a supertype for:

• all standard objects
• all custom objects
• all apex classes
• all collections (List, Set and Map)
• all apex types (Integer, String, Boolean)
• Methods inherited from Object class

SObject and Object

Sobject and object - instanceof.

• SObject is an instance of Object . Object is a supertype for SObject .

SObject and Object - casting

Object to sobject.

• Object needs to be explicitly cast to SObject .
• Object is a supertype of SObject .
• Conversion from Object to SObject is called Downcasting .
• As you already know from Downcasting section. Downcasting needs to be explicit (SObject) .

SObject to Object

• SObject can be explicitly or implicitly cast to Object .
• Conversion from SObject to Object is called Upcasting .
• As you already know from Upcasting section. Upcasting can be done explicitly or implicitly.

Inherited methods

• Interestingly, Object is a supertype for SObject , but SObject does NOT inherit Object methods like toString(), equals(), hashCode(), clone() . SObject has all of the following methods SObject class methods. .

However, all Apex Classes inherit Object methods ( toString() , equals() , hashCode() , clone() ).

Standard/Custom Object

Standard/custom object - instanceof.

• Standard/Custom Object is an instance of SObject and Object .
• SObject and Object are supertypes for Standard/Custom Objects .

Standard/Custom Object to SObject - casting

Standard/custom object to sobject.

Why it works?

• SObject is a supertype for Account , Contact , and other standard or custom objects.
• Conversion from Standard/Custom Object to SObject is called Upcasting .

SObject to Standard/Custom Object

• Conversion SObject to Standard/Custom Object is called Downcasting .
• As you already know from Downcasting section. Downcasting can be done ONLY explicitly.

Standard/Custom Object to Object - casting

Standard/custom object to object.

• Object is a supertype for Account , Contact , and other standard or custom objects.
• Conversion from Standard/Custom Object to Object is called Upcasting .

Object to Standard/Custom Object

• Conversion Object to Standard/Custom Object is called Downcasting .

Primitive Types

Primitive types - instanceof.

• All Primitive Data Types are instanceOf Object class.
• Object is a supertype for all primitve types.

Primitive Types - casting

• Primitive Types can be implicilty cast to Object .
• Object is a supertype of all Primitive Types.
• Conversion from Primitive Type to Object is called Upcasting .

List<SObject>

List<sobject> - instanceof.

• List<SObject> is an instance of concrete Standard/Custom Object!
• List<SObject> is NOT an instance of List<Object> .

List<SObject> - casting

List<sobject> to list<object>.

• List<SObject> is NOT an instance of List<Object> (based on instanceOf ), but you can still assign List<SObject> to List<Object> . Do not trust instanceOf !

List<Standard/Custom> to List<SObject>

• List<SObject> is a supertype for List<Standard/Custom> .
• Conversion from Standard/Custom Object to List<SObject> is called Upcasting .

List<SObject> to List<Standard/Custom>

Upcasting/Downcasting (?)

• List<Standard/CustomObject> is an instance of List<SObject> , and List<SObject> is an instance of List<Standard/CustomObject> .
• List<Standard/CustomObject> is a supertype for List<SObject> , and List<SObject> is a supertype for List<Standard/CustomObject> .
• You can do implicit casting.

List<Object>

List<object> - instanceof.

• SObject is always an instance of Object , hovever List<SObject> is NOT an instance of List<Object> .

List<Object> - casting

• We can cast List<ConcreteType> to List<Object> ,
• List<Object> is a supertype of List<ConcreteType> .
• Conversion from List<ConcreteType> to List<Object> is called Upcasting .
• There is no need to cast explicitly by adding (List<Object>) .
• List<SObject> is NOT an instance of List<Object> (based on instanceOf ), but you can still assign List<SObject> to List<Object> .

List Summary

List casting in Apex is a bit unusual.

What is common:

• List<ConcreteType> is an instance of List<Object> .
• List<Object> is a supertype for List<ConcreteType> .

What is unexpected:

• Based on instanceOf . List<SObject> is not an instance of List<Object> , but you can still assign List<SObject> to List<Object> .
• You can even assign List<SObject> to List<Object> . Do not trust instanceOf !
• Even more unexpectedly, List<SObject> is an instance of concrete List<Standard/Custom> Object!

Set<SObject>

Set<sobject> - instanceof.

• Set<Standard/CustomObject> is NOT an instance of Set<SObject> .

Set<SObject> - casting

Set<sobject> to set<object>.

• You CANNOT cast Set<SObject> to Set<Object>

Set<Standard/Custom> to Set<SObject>

• You CANNOT cast Set<Standard/Custom> to Set<SObject>

Set<SObject> to Set<Standard/Custom>

• You CANNOT cast Set<SObject> to Set<Standard/Custom>

Set<Object>

Set<object> - instanceof.

• Other than List , Set<Object> is NOT a supertype for Set<ConcreteType> .

Set<Object> - casting

• We CANNOT cast Set<ConcreteType> to Set<Object> ,

Even if you explicitly add casting (Set<Object>) it will not work.

Set Summary

Map<sobject>, map<sobject> - instanceof.

I skipped cases where SObject is a key. SObject should never be a key in the Map.

• Map<Object, Account> is an instance of Map<Object, Object> , which means that Map<Object, Object> is a supertype of Map<Object, Account> .
• Map<Object, Account> is an instance of Map<Object, SObject> , which means that Map<Object, SObject> is a supertype of Map<Object, Account> .

Map<SObject> - casting

• Map<Object, Object> is a supertype for Map<Object, Standard/CustomObject> .
• Conversion from Map<Object, Standard/CustomObject> to Map<Object, Object> is called Upcasting .

Even explicit casting will not work. The error is different.

How to fix Map downasting?

Map<Object>

Map<object> - instanceof.

Maps are the same instance only in the following cases:

• new Map<MyType, MyType>() instanceOf new Map<MyType, Object>
• new Map<Object, MyType>() instanceOf new Map<Object, Object>

Key Type must be the same.

Map<Object> - casting

You can cast implicitly only when:

Map Summary

Starting from Summer 23', Set implements Iterable interface as List does.

Iterable List

Iterable list - instanceof.

Not surprisingly, a List of concrete types is also an instance of Iterable<Object> .

• Instance of List<Object> and Set<Object> are always an instance of System.Iterable<Object> .

Iterable List - casting

It's really interesting.

e.g List<String> is an instance of Iterable<Object> , but you CANNOT use Iterable<Object> as a supertype .

You need to assign List<String> to List<Object> and after it to Iterable<Object> .

Iterable Set

Iterable set - instanceof.

• An interesting thing is that you're getting an error Operation instanceOf is always true... .
• Set<ConcreteType> is also an instance of Iterable<Object> , but not Set<SObject> .

Iterable Set - casting

• You CAN use Iterable<Object> as a supertype for Set , which you CANNOT do with a List .
• You CANNOT assign Set<SObject> to Iterable<Object> .

It's quite a big deal. Let's check an example:

How to fix it?

• You need two methods ( isIn(Iterable<Object> inList) and isIn(List<Object> inList) ) in the interface that will be covered by one method ( isIn(Iterable<Object> inList) in concrete class!

Iterable Summary

• You CANNOT use Iterable<Object> as a supertype for List<ConcreteType> . You need to assign List<ConcreteType> to List<Object> and after it to Iterable<Object> .
• Set<ConcreteType> is instance of Iterable<Object> .
• Set<Sobject> is NOT instance of Set<SObject> .

Casting Rules

Cast to everything.

The problem with the solution below is performance.

Casting Cheat Sheet

Do not trust instanceof.

Based on the type system is broken with regards to collections :

Pretty much the entire "Type" system that governs Maps, Sets, and Lists is broken. Do not trust instanceOf, use your own logical assessment to determine if something is safe or not.

As shown in the post, there are cases where instanceOf does not work correctly.

List<SObject> and List<Object>

instanceOf says that " List<SObject> is never an instance of List<Object> ", but you can assign List<SObject> to List<Object> .

List<ConcreteType> and Iterable<Object>

instanceOf says that List<ConcreteType> is an instance of Iterable<Object> , but you CANOT assign List<ConcreteType> to Iterable<Object> .

SObject Casting

• Casting from Standard/Custom Object to SObject is called upcasting and can be implicitly.
• Casting from SObject to Standard/Custom Object is called downcasting and it needs to be explicit.
• SObject is instance of Object . Object is a supertype for SObject .
• Casting from SObject to Object is called upcasting and can be implicit.
• Casting from Object to SObject is called downcasting and it needs to be explicit.

Object Casting

Primitive types casting.

• All Primitive Data Types are instanceOf Object . Object is a supertype for all primitve types.
• Casting from Primitive Data Types to Object is called upcasting and can be implicit.

List Casting

• All List<ConcreteType> are instance of List<Object> . List<Object> is a supertype of List<ConcreteType> .
• Based on instanceOf method List<SObject> is NOT an instance of List<Object> , but still you can assign List<SObject> to List<Object> . Do not trust instanceOf .
• Casting from List<ConcreteType> to List<Object> is called upcasting and can be implicit.
• List<Standard/Custom> is a supertype for List<SObject> .

Set Casting

• You CANNOT cast Set<ConcreteType> to Set<Object> .

Map Casting

• Map<Object, Account> is instance of Map<Object, Object> , it means that Map<Object, Object> is a supertype for Map<Object, Account> .
• Map<Object, Account> is instance of Map<Object, SObject> , it means that Map<Object, SObject> is a supertype for Map<Object, Account> .
• To fix System.TypeException: Invalid conversion from runtime type Map<ANY,SObject> to Map<ANY,Account> dynamic Map initiation is needed.

Iterable Casting

• Set<ConcreteType> is instance of Iterable<Object> , but Set<SObject> is NOT instance of Iterable<SObject> .
• Unexpected Iterable behavior in Apex
• Classes and Casting
• Using the instanceOf Keyword
• Upcasting Vs Downcasting in Java

You might also like

Advanced Salesforce LWC debugging with Chrome Developer Tools

LWC debugging and development with Chrome Developer Tools – learn how Salesforce LWC developer can debug and develop Lightning Web Components effectively without console.logs.

Beyond If Statements: Ways to avoid IFs – Polish Dreamin’ 24

Code is a representation of business requirements. Business requirements vary for each company, but most of them have an IF-THEN structure. It’s quite common to see IF statements in our code. However, an increasing number of IFs can make our code hard to read and understand.

Illegal assignment from String to Decimal

• 役に立った順で並び替え

Spot on for Amit

String temp = '12.4567';

Decimal myDecimal = Decimal.valueOf(temp);

System.assertEquals(12.4567,myDecimal);