Answered

Issue with import from a csv to a custom activity table

(0) Share

Report

Posted on by lwesley89

Hi Folks,

We have a custom activity table that we are wanting to import file notes to from a csv that was exported from a 3rd party platform we are moving away from. My test document has 11 records for a particular contact. I ran an import job, created a a data map and after processing it said 11 of 11 successful but when going through the table 2 of the records are missing.

After some testing I was able to identify that the missing records had a value of Open for the activity status field. If i changed the value in the csv to either closed or cancelled it would import correctly to the table but if set to Open it would not make it to the table. Does anyone have any ideas on how I might resolve this as I want to capture the status of the file notes for continuity purposes.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Sort by

gulshankhurana 1,397 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @lwesley89

What are the values for 'Activity Status' column and their respective 'Status Reason' values?
Are you including 'Status Reason' column also in your CSV table? If not, please include both the 'Activity Status' as well as it's respective 'Status Reason' for each record.

I hope this information helps. If it helps solve the query then please mark it as a solution otherwise please give it a Thumbs Up 👍🏻 anyways to support.

Kind regards
Gulshan

Was this reply helpful? Yes No
lwesley89 22 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @gulshankhurana,

Thank you for the reply. I had not considered the 'Status Reason' Column and did not include that in the csv as it didn't have anything data column like that from the other platform. I will investigate the usage of the 'Status Reason' and see if that helps.

Was this reply helpful? Yes No
Verified answer

lwesley89 22 on at

Like
a
(0)

Report
Copy link

Link copied!

I found there was an issue with the underlying table, it was a custom table made by a colleague. When importing to a fresh table it went flawlessly. Thankfully the original table had not been utilised so i simply deleted that table and used the new one.

Was this reply helpful? Yes No