Forum Discussion
Entities do not appear in Dataflow when creating Linked Entities
MS Product Team are aware of the issue with Dataflow entities not appearing in Desktop browser. They are planning on implementing a fix by the end of the week.
See thread:
I have had other issues with dataflows this week, and their tech team suggested I wait until next Monday and check again then. If there are issues remaining next week then submit a support ticket.
My issue is entities not appearing in Desktop or Service...Microsoft Support said the bug has been identified and the fix would take 4 weeks.
Trying to see if I can get them to find out more information from the product team about what's causing the issue--so maybe I can find a workaround instead of waiting a month to share my dataflows.
- jcullum6 years agoAdvocate II
jeffshieldsdev the attached thread as supplied by rargyle contains all the information required to workaround the issue. What you have described is consistent with everyone's issue (well not Doodle's new issue). Any entity containing a Date field is now being stored as "Unclassified". This results in new and existing Entity not appearing in the
Workaround:
Edit your dataflow, change all your Date fields to a data type of DateTime or Text, then your entities will appear in both the Service and Deskop. Change the data type field in the Desktop to back "Date" as required for relationships and visuals.
- jeffshieldsdev6 years agoSolution Sage
Right now I'm getting a 500 error trying to save dataflows--so I can't test now.
I don't have any Dates but a lot of DateTimes...I'll change them all to Text and see what happens. Thanks for the suggestion.
- jcullum6 years agoAdvocate II
jeffshieldsdev That sounds new. DateTime fields were working fine. I am not sure the change to text is going to fix your problem. I have been using a mixture of DateTime and Text.
In the Edit Dataflow web UI, expand the Entities (not to be confused with Editing the Entities) and make sure none of the fields are appearing as "Unclassified". Any that are you will need to fix by editing the entities.
As an aside.
I get a 500 error if I use the Web UI for the sharepoint.files connector. For some reason the UI doesn't include the [ApiVersion = 15] parameter. I have to use the advanced editor and manually add that into the connector. I have asked my internal team to raise that issue with MS also.
Good luck with it all.