Release candidate of OpenEMM 2011 available now

Use this forum to report bugs and to check for bugfixes and new releases of OpenEMM

Moderator: moderator

toni
Posts: 6
Joined: Tue Jul 05, 2011 2:18 pm

Re: Release candidate of OpenEMM 2011 available now

Post by toni » Thu Jul 07, 2011 3:10 pm

maschoff wrote:Please check if fix #2 works for you: https://sourceforge.net/projects/openem ... EMM%202011
Yes, thank you. It perfectly works!

toni
Posts: 6
Joined: Tue Jul 05, 2011 2:18 pm

Re: OpenEMM 2011: & bitwise operator support

Post by toni » Fri Jul 08, 2011 4:34 pm

Hi,

on the 'New Target Group' Page > 'New rule' would it be possible to add support for the Bitwise AND operator '&'?

This way I could store for each customer in a single field multiple values as bitmask and query them with the AND operator.
This would be a great help since it is not possible to have an extra relational table to store extra data for each customer.
(Since the list of extra data is long and can increase with the time, just adding new fields in the customer tbl is not an option)

E.g.
Imagine we have some preferences available that a customer can choose for his profile (stored as bitmask):

Code: Select all

 red -> 1
 black -> 2
 pink -> 4
 white -> 8
 green ->16
 .. 32
 ..
 
..so that for a customer that likes 'green' and 'black' we could store in a single field 'total_preferences' 18 (aka 16 + 2 )

And then to find out all customers who like 'green' and 'black' we could add rules as follows:

Code: Select all

 total_preferences & 16 = 16
 and total_preferences & 2 = 2
Thanks for your support or any suggestion how I can somehow store similar lists of customers' data.

toni
Posts: 6
Joined: Tue Jul 05, 2011 2:18 pm

OpenEMM 2011 RC2: bug webservice addSubscriber time store

Post by toni » Tue Jul 12, 2011 4:42 pm

Hi,

when I add a new subscriber via webservice addSubscriber() the time part of a 'date' field (timestamp or datetime for tbl customer_1_tbl in mysql) is not getting stored in the table. Only the date part is getting stored while the time part always remains: 00:00:00 (e.g login_date: 2011-07-08 00:00:00).

Notice that the Recipient Import via csv file doesnt have this problem. Datetime is always stored correctly.

See a soap request that doesnt store the time correctly:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
	xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<soapenv:Body>
		<ns1:addSubscriber soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
			xmlns:ns1="urn:agnitas-webservice">
			<in0 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">xxxx</in0>
			<in1 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">yyyy</in1>
			<in2 xsi:type="xsd:boolean">true</in2>
			<in3 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">account_id</in3>
			<in4 xsi:type="xsd:boolean">true</in4>
			<in5 href="#id0" />
			<in6 href="#id1" />
		</ns1:addSubscriber>
		<multiRef id="id0" soapenc:root="0"
			soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
			xsi:type="ns2:StringArrayType" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
			xmlns:ns2="urn:agnitas-webservice">
			<x xsi:type="xsd:string">email</x>
			<x xsi:type="xsd:string">gender</x>
			<x xsi:type="xsd:string">firstname</x>
			<x xsi:type="xsd:string">lastname</x>
			<x xsi:type="xsd:string">account_id</x>
			<x xsi:type="xsd:string">name</x>
			<x xsi:type="xsd:string">accountstate_id</x>
			<x xsi:type="xsd:string">birth_date_DAY_DATE</x>
			<x xsi:type="xsd:string">birth_date_MONTH_DATE</x>
			<x xsi:type="xsd:string">birth_date_YEAR_DATE</x>
			<x xsi:type="xsd:string">birth_date_HOUR_DATE</x>
			<x xsi:type="xsd:string">birth_date_MINUTE_DATE</x>
			<x xsi:type="xsd:string">birth_date_SECOND_DATE</x>
			<x xsi:type="xsd:string">login_date_DAY_DATE</x>
			<x xsi:type="xsd:string">login_date_MONTH_DATE</x>
			<x xsi:type="xsd:string">login_date_YEAR_DATE</x>
			<x xsi:type="xsd:string">login_date_HOUR_DATE</x>
			<x xsi:type="xsd:string">login_date_MINUTE_DATE</x>
			<x xsi:type="xsd:string">login_date_SECOND_DATE</x>
			<x xsi:type="xsd:string">account_create_date_DAY_DATE</x>
			<x xsi:type="xsd:string">account_create_date_MONTH_DATE</x>
			<x xsi:type="xsd:string">account_create_date_YEAR_DATE</x>
			<x xsi:type="xsd:string">account_create_date_HOUR_DATE</x>
			<x xsi:type="xsd:string">account_create_date_MINUTE_DATE</x>
			<x xsi:type="xsd:string">account_create_date_SECOND_DATE</x>
			<x xsi:type="xsd:string">apps_installed</x>
		</multiRef>
		<multiRef id="id1" soapenc:root="0"
			soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
			xsi:type="ns3:StringArrayType" xmlns:ns3="urn:agnitas-webservice"
			xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
			<x xsi:type="xsd:string">Andy@xx.intern</x>
			<x xsi:type="xsd:string">0</x>
			<x xsi:type="xsd:string">Andy </x>
			<x xsi:type="xsd:string">Nachname</x>
			<x xsi:type="xsd:string">15000003</x>
			<x xsi:type="xsd:string">Andy</x>
			<x xsi:type="xsd:string">1</x>
			<x xsi:type="xsd:string">08</x>
			<x xsi:type="xsd:string">12</x>
			<x xsi:type="xsd:string">1989</x>
			<x xsi:type="xsd:string">0</x>
			<x xsi:type="xsd:string">0</x>
			<x xsi:type="xsd:string">0</x>
			<x xsi:type="xsd:string">12</x>
			<x xsi:type="xsd:string">07</x>
			<x xsi:type="xsd:string">2011</x>
			<x xsi:type="xsd:string">16</x>
			<x xsi:type="xsd:string">26</x>
			<x xsi:type="xsd:string">28</x>
			<x xsi:type="xsd:string">29</x>
			<x xsi:type="xsd:string">04</x>
			<x xsi:type="xsd:string">2011</x>
			<x xsi:type="xsd:string">19</x>
			<x xsi:type="xsd:string">23</x>
			<x xsi:type="xsd:string">15</x>
			<x xsi:type="xsd:string">#3#4#7#8#11#22#23#34#</x>
		</multiRef>
	</soapenv:Body>
</soapenv:Envelope>


Post Reply