<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: [IOS]Missing fields using the 4.0 API on submit in Adobe Experience Cloud Mobile Questions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205955#M94</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.6em;"&gt;Hey Filipe,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In order for your context data to be usable in your props, eVars, etc, it must have appropriate mappings. &amp;nbsp;Have you created processing rules to map your context data to the correct variables? &amp;nbsp;You can read more about processing rules here:&amp;nbsp;&lt;A href="https://marketing.adobe.com/resources/help/en_US/mobile/ios/proc_rules.html" target="_blank"&gt;https://marketing.adobe.com/resources/help/en_US/mobile/ios/proc_rules.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, here is a migration guide that should help answer some questions as you transition from 2.x to 4.x:&amp;nbsp;&lt;A href="https://marketing.adobe.com/resources/help/en_US/mobile/ios/migration_v3.html" target="_blank"&gt;https://marketing.adobe.com/resources/help/en_US/mobile/ios/migration_v3.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;steve benedick&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;mobile software engineer&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.adobe.com/solutions/digital-marketing.html" target="_blank"&gt;Adobe Marketing Cloud&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Oct 2015 02:26:07 GMT</pubDate>
    <dc:creator>steve_benedick</dc:creator>
    <dc:date>2015-10-16T02:26:07Z</dc:date>
    <item>
      <title>[IOS]Missing fields using the 4.0 API on submit</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205953#M92</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&lt;STRONG&gt;Hi!&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&lt;STRONG&gt;I making the migration from 2.X client to 4.x. I want to keep the old name fields so I'm mapping with the same keys on nsdictionary. It's generating a request similar to the next:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;BR /&gt;&lt;SPAN class="s1"&gt;&lt;STRONG&gt;&amp;nbsp;ADBMobile Debug: Analytics - Successfully sent hit(ndh=1&amp;amp;t=xxxxxx&amp;amp;c.&amp;amp;prop75=D%3DUser-Agent&amp;amp;prop22=portfolio%3Ahome%3Achangenumber&amp;amp;channel=portfolio%3Ahome&amp;amp;eVar5=D%3Dc6&amp;amp;prop7=logged%20out&amp;amp;prop74=portfolio%3Ahome&amp;amp;eVar52=D%3DpageName&amp;amp;prop21=portfolio%3Ahome%3Achangenumber&amp;amp;prop6=xxxx&amp;amp;pageName=xxxx%3Aportfolio%3Ahome&amp;amp;prop28=iOS&amp;amp;userAgent=Mozilla%2F5.0%20%28iPhone%3B%20CPU%20iPhone%20OS%208_3%20like%20Mac%20OS%20X%29%20AppleWebKit%2F600.1.4%20%28KHTML%2C%20like%20Gecko%29%20Mobile%2F12F69&amp;amp;prop23=portfolio%3Ahome%3Achangenumber&amp;amp;timestamp=1431541341&amp;amp;prop5=Self%20Service&amp;amp;eVar23=D%3Dc28&amp;amp;prop19=Simulator&amp;amp;eVar8=D%3Dc9&amp;amp;eVar12=D%3Dc74&amp;amp;prop25=iOS%20APP%xxxxx%xxxxx%xxxxx%202.4.5&amp;amp;eVar62=D%3Dc19&amp;amp;a.&amp;amp;action=xxxxx%xxxxxx%3Ahome&amp;amp;OSVersion=iOS%208.3&amp;amp;DeviceName=x86_64&amp;amp;CarrierName=%28null%29&amp;amp;AppID=xxxxxxx%202.4.5%20%282.4.5%29&amp;amp;RunMode=Application&amp;amp;Resolution=640x1136&amp;amp;TimeSinceLaunch=629&amp;amp;.a&amp;amp;hier1=portfolio%3Ahome&amp;amp;.c&amp;amp;pev2=AMACTION%xxxxxx%3Aportfolio%3Ahome&amp;amp;ts=1431537741&amp;amp;pageName=xxxxxx%2F2.4.5&amp;amp;aid=xxxxxxx&amp;amp;ce=UTF-8&amp;amp;pe=lnk_o)&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;Some companies identity elements was replaced&amp;nbsp;by xxxx.&lt;/P&gt;&lt;P class="p1"&gt;On the platform all the fields are as unknown. Probably I'm missing this fields key.&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;Thanks for your help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:26:07 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205953#M92</guid>
      <dc:creator>filipet60049002</dc:creator>
      <dc:date>2015-10-16T02:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: [IOS]Missing fields using the 4.0 API on submit</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205954#M93</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;&lt;IMG src="https://experienceleaguecommunities.adobe.com/etc/designs/adobeforums/images/icons/quote-arrows.png" /&gt;&lt;P class="quote-text" contenteditable="false"&gt;&lt;CODE&gt;&lt;SPAN class="quote-author"&gt;Filipe Teixeira&lt;/SPAN&gt; wrote...&lt;/CODE&gt;&lt;/P&gt;&lt;CODE&gt; &lt;/CODE&gt;&lt;P class="p1"&gt;&lt;CODE&gt;&lt;SPAN class="s1"&gt;&lt;STRONG&gt;Hi!&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/P&gt;&lt;CODE&gt; &lt;/CODE&gt;&lt;P class="p1"&gt;&lt;CODE&gt;&lt;SPAN class="s1"&gt;&lt;STRONG&gt;I making the migration from 2.X client to 4.x. I want to keep the old name fields so I'm mapping with the same keys on nsdictionary. It's generating a request similar to the next:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/P&gt;&lt;CODE&gt; &lt;/CODE&gt;&lt;P class="p1"&gt;&lt;BR /&gt;&lt;CODE&gt;&lt;SPAN class="s1"&gt;&lt;STRONG&gt;&amp;nbsp;ADBMobile Debug: Analytics - Successfully sent hit(ndh=1&amp;amp;t=xxxxxx&amp;amp;c.&amp;amp;prop75=D%3DUser-Agent&amp;amp;prop22=portfolio%3Ahome%3Achangenumber&amp;amp;channel=portfolio%3Ahome&amp;amp;eVar5=D%3Dc6&amp;amp;prop7=logged%20out&amp;amp;prop74=portfolio%3Ahome&amp;amp;eVar52=D%3DpageName&amp;amp;prop21=portfolio%3Ahome%3Achangenumber&amp;amp;prop6=xxxx&amp;amp;pageName=xxxx%3Aportfolio%3Ahome&amp;amp;prop28=iOS&amp;amp;userAgent=Mozilla%2F5.0%20%28iPhone%3B%20CPU%20iPhone%20OS%208_3%20like%20Mac%20OS%20X%29%20AppleWebKit%2F600.1.4%20%28KHTML%2C%20like%20Gecko%29%20Mobile%2F12F69&amp;amp;prop23=portfolio%3Ahome%3Achangenumber&amp;amp;timestamp=1431541341&amp;amp;prop5=Self%20Service&amp;amp;eVar23=D%3Dc28&amp;amp;prop19=Simulator&amp;amp;eVar8=D%3Dc9&amp;amp;eVar12=D%3Dc74&amp;amp;prop25=iOS%20APP%xxxxx%xxxxx%xxxxx%202.4.5&amp;amp;eVar62=D%3Dc19&amp;amp;a.&amp;amp;action=xxxxx%xxxxxx%3Ahome&amp;amp;OSVersion=iOS%208.3&amp;amp;DeviceName=x86_64&amp;amp;CarrierName=%28null%29&amp;amp;AppID=xxxxxxx%202.4.5%20%282.4.5%29&amp;amp;RunMode=Application&amp;amp;Resolution=640x1136&amp;amp;TimeSinceLaunch=629&amp;amp;.a&amp;amp;hier1=portfolio%3Ahome&amp;amp;.c&amp;amp;pev2=AMACTION%xxxxxx%3Aportfolio%3Ahome&amp;amp;ts=1431537741&amp;amp;pageName=xxxxxx%2F2.4.5&amp;amp;aid=xxxxxxx&amp;amp;ce=UTF-8&amp;amp;pe=lnk_o)&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/P&gt;&lt;CODE&gt; &lt;/CODE&gt;&lt;P class="p1"&gt;&lt;CODE&gt;&amp;nbsp;&lt;/CODE&gt;&lt;/P&gt;&lt;CODE&gt; &lt;/CODE&gt;&lt;P class="p1"&gt;&lt;CODE&gt;Some companies identity elements was replaced&amp;nbsp;by xxxx.&lt;/CODE&gt;&lt;/P&gt;&lt;CODE&gt; &lt;/CODE&gt;&lt;P class="p1"&gt;&lt;CODE&gt;On the platform all the fields are as unknown. Probably I'm missing this fields key.&amp;nbsp;&lt;/CODE&gt;&lt;/P&gt;&lt;CODE&gt; &lt;/CODE&gt;&lt;P class="p1"&gt;&lt;CODE&gt;&amp;nbsp;&lt;/CODE&gt;&lt;/P&gt;&lt;CODE&gt; &lt;/CODE&gt;&lt;P class="p1"&gt;&lt;CODE&gt;Thanks for your help.&lt;/CODE&gt;&lt;/P&gt;&lt;CODE&gt; &lt;/CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P class="p" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); padding: 0px; color: rgb(75, 75, 75); font-family: AdobeClean; font-size: 16px; line-height: normal;"&gt;&lt;STRONG class="ph b" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0);"&gt;Events, Props, eVars&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="p" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); padding: 0px; color: rgb(75, 75, 75); font-family: AdobeClean; font-size: 16px; line-height: normal;"&gt;If you've looked at the&amp;nbsp;&lt;A class="xref" href="https://marketing.adobe.com/resources/help/en_US/mobile/ios/methods.html#concept_12F12E3E0E434F8CB997AF4027810EBF" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); color: rgb(100, 135, 195); text-decoration: none;" target="_blank" title="Methods and classes provided by the iOS library."&gt;Methods and Classes&lt;/A&gt;, you are probably wondering where to set events, eVars, props, heirs, and lists. In version 4, you can no longer assign those types of variables directly in your app. Instead, the SDK uses context data and processing rules to map your app data to Analytics variables for reporting.&lt;/P&gt;&lt;P class="p" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); padding: 0px; color: rgb(75, 75, 75); font-family: AdobeClean; font-size: 16px; line-height: normal;"&gt;Processing rules provide you several advantages:&lt;/P&gt;&lt;UL class="ul" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); padding-right: 0px; padding-left: 0px; margin: 8px 20px 20px; color: rgb(75, 75, 75); font-family: AdobeClean; font-size: 16px; line-height: normal;"&gt;&lt;LI class="li" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); padding-bottom: 0px; margin: 8px 0px 0px;"&gt;You can change your data mapping without submitting an update to the App Store.&lt;/LI&gt;&lt;LI class="li" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); margin: 8px 0px 0px; padding-bottom: 0px;"&gt;You can use meaningful names for data instead of setting variables that are specific to a report suite.&lt;/LI&gt;&lt;LI class="li" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); margin: 8px 0px 0px; padding-bottom: 0px;"&gt;There is little impact to sending in extra data. These values won’t appear in reports until they are mapped using processing rules.&lt;/LI&gt;&lt;/UL&gt;&lt;P class="p" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); padding: 0px; color: rgb(75, 75, 75); font-family: AdobeClean; font-size: 16px; line-height: normal;"&gt;See&amp;nbsp;&lt;A class="xref" href="https://marketing.adobe.com/resources/help/en_US/mobile/ios/proc_rules.html#concept_4DAF0756D0DB43BD8C0627E023665FA5" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); color: rgb(100, 135, 195); text-decoration: none;" target="_blank"&gt;Processing Rules and Context Data&lt;/A&gt;.&lt;/P&gt;&lt;P class="p" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); padding: 0px; color: rgb(75, 75, 75); font-family: AdobeClean; font-size: 16px; line-height: normal;"&gt;Any values that you were assigning directly to variables should be added to the&amp;nbsp;&lt;SAMP class="ph codeph" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0);"&gt;data&lt;/SAMP&gt;&amp;nbsp;NSDictionary instead. This means that calls to&amp;nbsp;&lt;SAMP class="ph codeph" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0);"&gt;setProp&lt;/SAMP&gt;,&lt;SAMP class="ph codeph" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0);"&gt;setEvar&lt;/SAMP&gt;, and assignments to persistent context data should all be removed and the values added to the&amp;nbsp;&lt;SAMP class="ph codeph" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0);"&gt;data&lt;/SAMP&gt;&amp;nbsp;parameter.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); padding: 0px; color: rgb(75, 75, 75); font-family: AdobeClean; font-size: 16px; line-height: normal;"&gt;Also, we have heard that some of you are naming context data keys using the evar or prop number:&lt;/P&gt;&lt;DIV class="syntax-container" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); position: relative; padding: 0.5em 2pt; font-size: 0.85em; color: rgb(75, 75, 75); font-family: AdobeClean; line-height: normal;"&gt;&lt;OL class="syntax highlighted" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); font-family: Menlo, Monaco, Consolas, monospace; line-height: 1.5em; border: 1px solid rgb(170, 170, 170); padding-right: 0px !important; padding-left: 2.75em !important; margin: 0px !important; background-color: rgb(227, 227, 227);"&gt;&lt;LI class="alt line ln1 first" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); color: rgb(151, 151, 151); white-space: pre-wrap; word-wrap: break-word; padding-top: 0px !important; padding-right: 0px !important; padding-bottom: 0px; padding-left: 0px !important; margin: 8px 0px 0px;"&gt;&lt;DIV class="javascript source" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); color: rgb(51, 51, 51); margin-left: -0.5em; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(170, 170, 170); padding: 0px 0.4em !important; background-color: rgb(245, 245, 245);"&gt;&lt;SPAN class="javascript" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0);"&gt;&lt;SPAN class="string" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); color: rgb(28, 0, 206);"&gt;"eVar1"&lt;/SPAN&gt;:&lt;SPAN class="string" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); color: rgb(28, 0, 206);"&gt;"jimbo"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;DIV class="toolbar" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); position: relative; padding: 0px 0.2em 0.2em; border-bottom-style: none; font-size: 10.8800001144409px; text-align: right;"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P class="p" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); padding: 0px; color: rgb(75, 75, 75); font-family: AdobeClean; font-size: 16px; line-height: normal;"&gt;This might make it&amp;nbsp;&lt;EM class="ph i" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0);"&gt;slightly&lt;/EM&gt;&amp;nbsp;easier when you perform the one time mapping in processing rules&lt;BR /&gt;&lt;BR /&gt;Al the documentation indicates, that I should be able to use it directly on data, what maps are you talking about?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:26:07 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205954#M93</guid>
      <dc:creator>filipet60049002</dc:creator>
      <dc:date>2015-10-16T02:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: [IOS]Missing fields using the 4.0 API on submit</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205955#M94</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.6em;"&gt;Hey Filipe,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In order for your context data to be usable in your props, eVars, etc, it must have appropriate mappings. &amp;nbsp;Have you created processing rules to map your context data to the correct variables? &amp;nbsp;You can read more about processing rules here:&amp;nbsp;&lt;A href="https://marketing.adobe.com/resources/help/en_US/mobile/ios/proc_rules.html" target="_blank"&gt;https://marketing.adobe.com/resources/help/en_US/mobile/ios/proc_rules.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, here is a migration guide that should help answer some questions as you transition from 2.x to 4.x:&amp;nbsp;&lt;A href="https://marketing.adobe.com/resources/help/en_US/mobile/ios/migration_v3.html" target="_blank"&gt;https://marketing.adobe.com/resources/help/en_US/mobile/ios/migration_v3.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;steve benedick&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;mobile software engineer&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.adobe.com/solutions/digital-marketing.html" target="_blank"&gt;Adobe Marketing Cloud&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:26:07 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205955#M94</guid>
      <dc:creator>steve_benedick</dc:creator>
      <dc:date>2015-10-16T02:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: [IOS]Missing fields using the 4.0 API on submit</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205956#M95</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Usually I don't dump at forums entries, but in this case will require for assistance since the documentation is not clear on importing old evar or proper to the new suite.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Actually there is no entries at analytics, but they&amp;nbsp;are being sent by the clients, I even&amp;nbsp;can see them at bloodhound.&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Old clients works just fine. But since there is no 64bits support to old version I really need a solution to this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:26:07 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205956#M95</guid>
      <dc:creator>filipet60049002</dc:creator>
      <dc:date>2015-10-16T02:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: [IOS]Missing fields using the 4.0 API on submit</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205957#M96</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.6em;"&gt;Hey Filipe,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;In case you're still looking for it, here is the documentation for how you can map your context data to custom variables via processing rules using Adobe Mobile Services:&lt;/P&gt;&lt;P&gt;&lt;A href="https://marketing.adobe.com/resources/help/en_US/mobile/settings_custom_data.html" target="_blank"&gt;https://marketing.adobe.com/resources/help/en_US/mobile/settings_custom_data.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0.5em 0px 0.9em; padding: 0px; font-family: adobe-clean, 'Helvetica Neue', Arial, sans-serif; color: rgb(79, 80, 81); font-size: 14px; line-height: normal;"&gt;&lt;STRONG&gt;steve benedick&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin: 0.5em 0px 0.9em; padding: 0px; font-family: adobe-clean, 'Helvetica Neue', Arial, sans-serif; color: rgb(79, 80, 81); font-size: 14px; line-height: normal;"&gt;&lt;EM&gt;mobile software engineer&lt;/EM&gt;&lt;/P&gt;&lt;P style="margin: 0.5em 0px 0.9em; padding: 0px; font-family: adobe-clean, 'Helvetica Neue', Arial, sans-serif; color: rgb(79, 80, 81); font-size: 14px; line-height: normal;"&gt;&lt;A href="http://www.adobe.com/solutions/digital-marketing.html" style="color: rgb(58, 145, 215); cursor: pointer; text-decoration: none;" target="_blank"&gt;Adobe Marketing Cloud&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:26:07 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-cloud-mobile/ios-missing-fields-using-the-4-0-api-on-submit/m-p/205957#M96</guid>
      <dc:creator>steve_benedick</dc:creator>
      <dc:date>2015-10-16T02:26:07Z</dc:date>
    </item>
  </channel>
</rss>

