Skip to main content
Solved

Import Scenario to “Employee Time Activities” screen


Forum|alt.badge.img

Hello, I am new to Acumatica.

I am building an import Scenario for the “Employee Time Activities” screen.
The data is coming-in via a .CSV file (provided by an external source).
The Project number is coming-in from the .CSV file non-segmented.
The Project number segmented in Acumatica. (xx-xx-xxxxx). 

I have tried this two ways (in the .CSV file):

  1. Project number as segmented. Result: Field: Project, Value: SP-21-095, Error: 'Year' of 'Project' does not exist in the system.
  2. Project number as non-segmented. Result: error: Nullable object must have a value

When manually entering an Employee Time Activity record, I notice that Acumatica inserts default values the following columns: Hold, Status, Data, Time, Earning Type,
Time Spent, Billable, Billable Time,


and then copies values from the previous record columns: Project, Project Task, and Description.

It was suggested to me that bringing in the Project number as non-segmented was preferred.

 

Has anyone encountered the two errors (above) before?

How did you resolve?

Can you point me to an online reference that is related?

 

Thank you in advance.

-Ken Severud 

Best answer by vkumar

Hi @kseverud34 

Made slight changes, you can compare with previous one. Let me know if this works.

Regards,

View original
Did this topic help you find an answer to your question?

10 replies

Forum|alt.badge.img+11
  • Acumatica Support Team
  • 783 replies
  • December 9, 2021

Hi @kseverud34 

Since the Project segment key has multiple segments, Acumatica automatically try determine the segment value from the string supplied for Project ID. 

Looks like you have enabled ‘validate’ for the segment key ‘Year’. 

  • If you prefer to keep ‘validate’ enabled for the segment key, do enter values on Segment values (CS203000) screen in advance (the one you have on your import data, in this case 21??)
  • Else, you can disable ‘validate’ on Segment key screen for Project segment, that will allow you import any value without a need to set them in advance on Segment value screen. 

Hope this helps,

 


Forum|alt.badge.img
  • Jr Varsity III
  • 29 replies
  • December 9, 2021

Also, the dashes in the field are just a mask.  Try importing the field without any dashes in the data.  I have had to do that for segmented keys before.


Forum|alt.badge.img
  • Author
  • Freshman II
  • 11 replies
  • December 9, 2021

Thank you VijayKumarU and MRoszkowski15. I used both answers. I appreciate your help!! 


Forum|alt.badge.img+11
  • Acumatica Support Team
  • 783 replies
  • December 9, 2021

Hi @kseverud34 

Were you able to get the issue resolved with the input? Curious to know if the issue has been sorted at your end. 

Regards,


Forum|alt.badge.img
  • Author
  • Freshman II
  • 11 replies
  • December 9, 2021

Hi vkumar, (thanks again for your help) It’s moving along but, I am still chasing down the error: Nullable object must have a value

It appears that there is a default value (that is not in my import file) that Acumatica must have to pass validation. Debugging that now.

 


Forum|alt.badge.img+11
  • Acumatica Support Team
  • 783 replies
  • December 9, 2021

Hi @kseverud34 

Please provide your import scenario xml file to review. 
Regards,


Forum|alt.badge.img
  • Author
  • Freshman II
  • 11 replies
  • December 9, 2021

Hi vkumar, I have included my import Scenario and the the .CSV file that I am using.

Thank you in advance for your review.

-ken


Forum|alt.badge.img+11
  • Acumatica Support Team
  • 783 replies
  • Answer
  • December 9, 2021

Hi @kseverud34 

Made slight changes, you can compare with previous one. Let me know if this works.

Regards,


Forum|alt.badge.img
  • Author
  • Freshman II
  • 11 replies
  • December 9, 2021

Hi VijayKumarU,

It appears that your changes have resolved my error: Nullable object must have a value. 
THANK YOU!!

I have some other Sample data (setup issues) to work through but I think I’m ok at the moment.

Best Regards,

-Ken Severud


HI @vkumar 

Can you please help me, i am getting also the same error . I tried your rectified import scenario and still experience the same issue.

I have attached my Import scenario.

Regards


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings