<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css"></style>
</head>
<body bgcolor="#FFFFFF" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi there,
<div><br>
</div>
<div>Actually, the dates are in the CSV file I'm importing. Here's an example I've been trying to work with :</div>
<div><br>
</div>
<div>
<div>"id","firstname","lastname","disabled","password","startDate","endDate","codeProgramme","employeeType"</div>
<div>"etudiantFutur1","Paul","Futur","false","ZsyOy","2016-01-01","2018-01-01","7316","Etudiant"</div>
<div>"etudiantPasse1","Isabelle","Passé","false","ujsCT","2010-01-01","2011-01-01","7316","Etudiant"</div>
<div>"etudiantActif1","Jean","Actif","false","b6pwa","2011-01-01","2017-01-01","7316","Etudiant"</div>
<div><br>
</div>
<div>As you can see, the dates are there and it seems like the parsing is successful. I tried changing the format to MM/DD/YY like so :</div>
<div><br>
</div>
<div>
<div>"etudiantActif1","Jean","Actif","false","b6pwa","01/20/11","01/20/17","7316","Etudiant"</div>
</div>
<div><br>
</div>
<div>But then, I get the following error which makes me believe the first example gets parsed correctly.</div>
<div><br>
</div>
<div>Failed to import: com.evolveum.midpoint.util.exception.SystemException: Synchronization action failed, reason: Unable to parse the date: 01/20/17</div>
<div><br>
</div>
<div>So, I guess the NPE has nothing to do with the parsing of the dates... </div>
<div><br>
</div>
<div>Vincent</div>
<div><br>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF549641" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>De :</b> midpoint-bounces@lists.evolveum.com [midpoint-bounces@lists.evolveum.com] de la part de Ivan Noris [ivan.noris@evolveum.com]<br>
<b>Date d'envoi :</b> 30 septembre 2013 03:59<br>
<b>À :</b> midPoint General Discussion<br>
<b>Objet :</b> Re: [midPoint] RE : RE : RE : RE : Namespace problem<br>
</font><br>
</div>
<div></div>
<div>Hi Vincent,<br>
<br>
regarding the schema: until recently, you could have only one schema for the same object extension, i.e. one schema file for User extension.<br>
<br>
This should be fixed now by <a class="moz-txt-link-freetext" href="https://jira.evolveum.com/browse/MID-1600" target="_blank">
https://jira.evolveum.com/browse/MID-1600</a> although I've not tried it yet, because my customers had not needed that until now. See the issue please for the target release information.<br>
<br>
As I understand you NPE, it happens when the times are empty/null when you import your data from CSV file?<br>
<br>
Regards,<br>
Ivan<br>
<br>
<div class="moz-cite-prefix">On 09/27/2013 11:05 PM, Belleville-Rioux, Vincent wrote:<br>
</div>
<blockquote type="cite"><style type="text/css"></style><style type="text/css"></style><style type="text/css"></style><style type="text/css"></style>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt"><font size="2" face="Tahoma">I found the TimeFrom and TimeTo configuration options and I am experimenting a NullPointerException with those...</font>
<div><font size="2" face="Tahoma"><br>
</font></div>
<div><font size="2" face="Tahoma">Attached : the shadow.xml file from an attempted import from CSV that shows the NPE. Also, the object template XML where the time-constrained mapping is present. The user extension I use for the startDate and endDate seems
to work because when I remove the time constraints, the import succeeds and I see the dates as (filled) date fields in the Users page. </font></div>
<div><font size="2" face="Tahoma"><br>
</font></div>
<div><font size="2" face="Tahoma">Any idea what's wrong ?</font></div>
<div><font size="2" face="Tahoma"><br>
</font></div>
<div><font size="2" face="Tahoma">Vincent</font></div>
<div><font size="2" face="Tahoma"><br>
</font>
<div style="font-family:Times New Roman; color:#000000; font-size:16px">
<hr tabindex="-1">
<div id="divRpF202968" style="direction:ltr"><font color="#000000" size="2" face="Tahoma"><b>De :</b>
<a class="moz-txt-link-abbreviated" href="mailto:midpoint-bounces@lists.evolveum.com" target="_blank">
midpoint-bounces@lists.evolveum.com</a> [<a class="moz-txt-link-abbreviated" href="mailto:midpoint-bounces@lists.evolveum.com" target="_blank">midpoint-bounces@lists.evolveum.com</a>] de la part de Belleville-Rioux, Vincent [<a class="moz-txt-link-abbreviated" href="mailto:rioux.vincent@uqam.ca" target="_blank">rioux.vincent@uqam.ca</a>]<br>
<b>Date d'envoi :</b> 27 septembre 2013 15:46<br>
<b>À :</b> midPoint General Discussion<br>
<b>Objet :</b> [midPoint] RE : RE : RE : Namespace problem<br>
</font><br>
</div>
<div>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">Please ignore my previous message as I found that we can't have more than one extension schema at the same time. I merged my added attributes to the extension-whatever.xsd and it
now works.
<div><br>
</div>
<div>I however have another question : how can we compare dates in mappings? I want to try and do a conditional mapping where the user start date is checked against today to see if the account should or should not be mapped to the role.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Vincent</div>
<style type="text/css">
<!--
-->
</style><style type="text/css">
<!--
-->
</style><style type="text/css" id="owaParaStyle">
<!--
-->
</style><style type="text/css">
<!--
-->
</style></div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader" target="_blank"></fieldset> <br>
<pre>_______________________________________________
midPoint mailing list
<a class="moz-txt-link-abbreviated" href="mailto:midPoint@lists.evolveum.com" target="_blank">midPoint@lists.evolveum.com</a>
<a class="moz-txt-link-freetext" href="http://lists.evolveum.com/mailman/listinfo/midpoint" target="_blank">http://lists.evolveum.com/mailman/listinfo/midpoint</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Ing. Ivan Noris
Consultant
Evolveum, s.r.o
___________________________________________________
"Semper cautus - semper paratus - semper idem Vix."
</pre>
</div>
</div>
</div>
</div>
</body>
</html>