Business Intelligence and Dynamics Solutions
Came to give quick tip on Dynamics 365 / CRM Two option set field in Dynamics Portal.
Previous post I showed on how to set value for option set field (Two option set)
Here you go for get the value from two option set.
$('input[name*=new_contactupdated]:checked’).val()
Hope it help you to reduce your time on searching this.
Please do share your thoughts on my posts to improve the content.
If you need anything on the Dynamics 365 and it’s related stuffs, please don’t hesitate to reach me.
Hope everyone is doing great ❤
Recently, I had a requirement to show / hide the Workflow button based on certain field value.
Portal has provision for it.
In Action button configuration advanced settings, we can find Filter Criteria text box. There you can put FetchXml filter condition.
Like below,
It does the magic on load of the form in Dynamics portal.
Hope it help somebody.
Dear All,
It’s been a while i haven’t write any post. Quite busy with office stuffs.
Currently busy working in Dynamics Portals and Dynamics 365 v9.0 with updated client API.
Here I would like to share quick tip on setting field values on Dynamics Portal. We know that lot of articles are flown in the google for get/set values. we cant find for Two options set fields in Dynamics 365/CRM.
Here is the snippet which works for it.
Two option set field is rendered as group radio button.
Hope this tip will help to save your time.
If you have any alternative approach, Please do share with me.
If you need a help, you can reach me at any time.
Friends,
I am so happy to connect with you all through blogging. In this Christmas time, I would like to share my work experience on the recent data migration project.
Core logic required was
Replacing comma separated GUID values in the column with the corresponding name for the GUID from the system
I should not use tables need to manipulate using flat files.
I did it as two-step:
Just like this below figure
for second step, i got a snippet from google search. It really reduced my development time for this work. Here is the link
Prototype is ready. While implementing the similar transformation, I just copied the data flow task and done the required changes.
While executing the whole package, faced two error (where the DFT-Data Flow Task pasted)
Error 1:
The value is too large to fit in the column data area of the buffer
Normally, this error comes if the source column length is greater than the destination column. I am sure in my project maintained the same.
I don’t have any clue, what’s wrong? Refreshed the component, multiple time build the script component project. No use..
Finally got the solution..Delete the script component and Create it 😀
Lesson learnt: DON’T COPY PASTE THE SCRIPT COMPONENT. Time wasting on development is better than debugging the error
Error 2:
The code in the above link will not handle empty rows. So I got error like this.
There is no current row in the buffer. A row may need to be added using the AddRow method.
Added code for validate the empty rows. Problem resolved.
That’s all from my end.
If you have any suggestions on this topic, please do share your thoughts.
Feel free to reach out to me If you need any help on data migration project / consulting.
Expertise in SSIS, Talend (ETL tool), Dynamics 365/CRM adapters – Kingswaysoft, Cozyroc, Scribe, OneTapAdapter.
Hello,
Hope everyone is doing awesome.
I believe everyone read my previous post.
If you haven’t read that, here it is Things-noticed-on-upgrading-from-v8-2-to-v9-0-part-1/
As part of upgrading, We tried importing of v8.2. solution.
Import fails:
Error 1:
In import wizard, it shows generic SQL error, try contact Administrator or Microsoft. I just downloaded the import log file and searched for error text.
Bingo!! Found something useful. Here is the error.
Entity Relationships – opportunity_parent_account – The nav pane properties for the entity relationship role a63574d6-42cc-e711-a835-000d3a1bea77 are not customizable
I felt that something wrong in this relationship. Checked out couldn’t find anything useful. While comparing the Customization.xml of this entity with previous version of the same, it sparked that there is a new set of XML tags are added to each relationship. Tried commenting that xml tags , it worked. But no idea, Why? Yet to do R&D on that.
Below xml code are commented which is part of this “<EntityRelationship Name=”opportunity_parent_account”>” tag.
Import is successfully passed this issue and got stuck in another one.
Error 2:
Process Action contains a parameter that is not supported. Name: {EntityName}, type: Entity, direction: Input
This is normal that we used to pass the entity as input. I dint feel something wrong in the input. I just deactivated the Action and imported back. Successfully imported.
In this release, i have faced these two issues. I just shared with you all.
Do share with me if you faced any issues in upgradation. I can update it to this post.
Feel free to reach out to me if you need any help on upgrade your project / consulting.
All,
Hope everyone doing great. It’s been a while. Pretty much busy in travels and new learnings.
Recently, we got requirement to upgrade from Dynamics 365 online v8.2. To v9.0 and client is using Dynamics 365 Native Mobile App heavily.
Most of them aware that few client side scripting Syntax are deprecated in v9.0.
How it will Impact if we migrate to v9.0.??
As we all know that we have typical form and Interactive form. We used to access the Interactive forms only through the interactive service hub url.
What’s the headache for the developers was need to design twice in earlier versions.
Now it’s changed in v9.0. Design once, Access traditional way or New Unified Interface aka Interactive Service Form.
As per Microsoft, new Unified Interface loads faster than the traditional one. We all know that Mobile App loads slower or takes time whenever login. It’s resolved in v9.0.
v9.0: Mobile App loads only the Unified Interface Sitemaps
Then how to define the Sitemaps as Unified Interface??
Yes, It has a property to switch between Web (traditional ) and Unified Interface.
One bottleneck in using Unified Interface is deprecated Syntax should be changed. Otherwise it will not work.
So make sure that all your client side scripts are using newer Syntax if you wish to utilize the Unified Interface feature. Otherwise it will work as usual in Web (Traditional ) after the upgrade also. But it will not work in Mobile App. As I mentioned above, Mobile app relies on Unified Interface.
If you have lot of custom ribbon buttons, that may be visible in unified interface or may not. So need to check your code and display rules.
We faced some difficulties in importing solutions to v9.0. I will keep you posted on new issues and errors on upgrade.
Highlights:
Still we haven’t completed the upgrade. We need to update the deprecated syntaxes. Then only we can complete the activity. I will post on those.
Am writing this post through mobile. Kindly bear me, couldn’t share screenshot.
Feel free to reach out to me if you need any help on upgrade your project / consulting.
See you all in next detailed post.
One of the day to day activities of developers is bug fixing and its releases to different environments.
When there is no version controller,no package deployment, How do we track the fixes in solutions.
Definitely we will work on lot of bugs. So keep track on the bugs which you are working.
How do we track then? Make an excel sheet, track the changes in a column, what are all items need to move for fixes and its releases.
Do you think it is easy to track like this. When multiple developers are working on bug fixing. How do we merge? How do we prepare the deployment package?
OmG! There is a chance for missing lot of things or overwrite on other’s work or latest changes are not moved.
Use version controller and package deployment model. Keep spoc for all deployment activities.
How do we manage solutions?
Lot of ways to manage your solutions, bug fixes, hot fixes.
Finalize the way, make the developers to follow the strategy to keep up their work and track their fixes accordingly.
It helps in many ways to reduce the re-work time..
Might be a small tip, but keeping routine which helps to use our resources time efficiently.
Business Rule – Check list
If you have any tips, please share me in comments.
Detailed post for Recurring jobs strategies
Good Morning !!
Hope everyone doing awesome.
Would like to share this tip with you all.
I believe everyone knows how to debug custom Workflows using Plugin Registration tool.
Trick is that while trying to profile, you will not be able to find steps for that respective workflow assembly.
Check: Whether you have used this assembly in workflow ?
Most of the time, we would have used in workflow. if it’s not working only, we used to come for debugging.:-;
No ? Start using it ..Then only steps will be visible in Plugin Registration tool.
Still steps are not visible n PR tool.
Yes ? Check whether you used this Custom Workflow assembly in conditional approach. If so, it will not be visible. So workaround will be use straight way in work flow.debug it. Fix your code.
Hope this tip will help to save your time in analysing it. If you have Better way, please do share me.
Thanks for reading and keep sharing. Happy Blogging.