mscrmtools / javista.attributesfactory Goto Github PK
View Code? Open in Web Editor NEWA, XrmToolBox plugin to manage attributes from an Excel spreadsheet
License: GNU General Public License v3.0
A, XrmToolBox plugin to manage attributes from an Excel spreadsheet
License: GNU General Public License v3.0
I would like to use this template to be part of my design documentation, but the nomenclature of attributes (ex: OptionSet vs Choice) is not consistent with the current version of D365. There is no chance that MS will go back to the "classic" attribute data types any time soon. Please update the tool to use the current data type names.
Hi,
First of all, great tool, makes creating Power Apps a lot more pleasant. I was, however, wondering if you were planning to implement functionality for formula type columns in the near future?
Kind regards,
Arne
Hi,
Once again a feature request from me. When exporting table information it would be very useful to be able to filter on whether a column is included in a specific form or alternatively excluded from a particular form. Especially the excluded from one (or more) form would be very useful in combination with the new delete column functionality. Then, we could easily export all columns of the table which are not part of our forms of interest and choose which we should delete from a much shorter list. The Metadata Document Generator implements this kind of filtering, therefore it should at least be possible, even though I do not know difficult it would be to implement.
Kind regards,
Arne
Hi,
I'm not able to create new columns from the template. I am getting the "Object reference not set to an instance of an object" error.
Current existing fields will get updated, but new columns I'm trying to create are not working.
Hi,
Another feature request from me in quick succession of the previous. It would be quite useful if the tool also allowed for easy deletion of columns. Until now I've been using Attribute Manager for this, but when a lot of columns are to be deleted it is both quite tedious and time consuming as you have to go through the process of doing this for every single one of them.
My initial thought would be to add another choice to the Action column (add "Delete" or something in addition to "Ignore" and "Process"). This would match very well with the already included export functionality of the tool, where we could just export the table information to Excel and then quickly select action "Delete" for those columns we want removed.
Is this something that would be difficult to implement?
Kind regards,
Arne
Hi guys! How are you? Hope you're fine! ;)
So I'm using the tool to create a calculated field but even filling the excel sheet correctly, the new field is created "bugged".
Instead of the new attribute have the "Calculated" field type it was created with the "Simple" one.
Please check the prints.
Could u help me, please!?
Tks in advance.
In the template, on cell N2, there's a note with a link back to Jona Rapp's website. That page doesn't exist anymore.
How do you modify an N: N relationship?
Hi Tanguy and everyone!
We noticed a very annoying behavior of the data dictionary regarding the Choice(s) (Option sets) when multi-languages is involved.
First, here are some information about our context : we're developing multi-language applications (French and English) using a Dataverse having French as its primary language and English as secondary.
When updating an existing Choise(s) (for example when adding a value) the English translations are deleted for all already existing values :-(
In our understanding, the Attribute Factory seems not considering multi-languages; this is just like if it were working only with the primary language of the Dataverse. Is it right?
Would it be possible to enhance the data dictionary to allow providing all the multi-languages texts in all the managed languages? For example by entering a text in a cell as a list of pairs containing the language code and the corresponding text.
Looking forward for your feedback and many thanks in advance !
Joyeux Noël et excellentes fêtes de fin d'année.
Steps to repro
Expected Result
The display name of the OptionSet is updated
Actual Result
The process failed with "Could not find an option set with the specified name: xyz_OptionSetAttributeLogicalName"
When creating large numbers of attributes on an on-prem CRM server, other users working in CRM experience slowdowns, time-outs, etc. IIS CPU usage is spiking and I'm not sure if there are database table locks being created on the back-end as the columns are being added to the back end. We've boosted RAM & CPU on CRM and SQL servers which seems to have helped but not eliminated the problem.
It's not always feasible to schedule entity creation for out-of-hours, so it would be really useful to have a 'throttle' option where the tool pauses for a few seconds between each attribute it processes, to allow IIS to serve other user requests and minimise these effects, at the expense of taking longer to process the spreadsheet overall.
Hi,
Your tool is just amazing !! and to make it even more fantastic, would it be possible to add the following feature:
when selecting the file to load and when clicking on the "..." button, the sole extension that appears to be allowed is ".xlsx" but we can type "*.*" + return to be able to select any kind of file.
Could you also allow the file extension ".xlsm" (or even "*.*") ? because I would like to use an Excel file with VBA logic inside that will display, according to our naming conventions, an error message in the status bar when I change the content of a "Schema name". This new feature will ease usage by my colleagues.
Thks in advance and best regards.
I'm using your template and I'm trying desperately to create a new field that must reuse an existing Global Choice.
As the columns headers comments are not crystal clear to me, I've tried all the possible combinations but none is working !... perhaps a bug is hiding behind ?
If I want to create a new field called "new_field" that must reuse the existing Global Choice called "new_gender_code", I will set column C to "new_field" and column D to "Choice"... and could you please explain what must be set in the columns P and Q ?
Many thanks in advance for your help, and all the best.
Hi MscrmTools!
Whether it is possible to create the corresponding entity according to a sheet table, and can automatically create the entity!This makes it easy to manage and maintain. @MscrmTools
When I export an entity with Currency fields, it includes the (Base) fields, so I have to remove them from the template before I import them. The same happens for rollup fields - I get the field's (Last Updated) and (State) fields, which would not be created in the target environment. You can see this happening when you export the Account entity.
You have an option to "Load also system columns" and I did leave that unchecked. Can you skip those system-managed fields when that field is not checked?
Whenever I create a lookup via the template and set the Required Level to "System Required" it works perfectly for all field types except for Lookup's which are always created as "Optional"!
I created a bunch of lookups and date/time fields, all with the "Enabled for audit" =yes, but the lookups did not get configured with FLS turned on.
Hi!
Im having some troubles creating choice fields, well, i dont really know how to write the options in the template, it only takes the first value. I dont understand when it says 'one row per value'. Can someone post any example?
In the Schema field, I use a formula to make it easier to just paste the Display Names
=CONCAT("new_",SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE((SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(B3,"/","")," ",""),")","")),"(",""),"#",""),"?",""),"'",""))
Could you include that in the base template?
It would be nice to be able to optionally provide the schema name to be used when generating a relationship. The default naming gets really long with redundant prefixes and depending the schema lengths, this can max out the generated schema name resulting in an error. When creating a relationship in the UI, the schema name is limited to 45 characters and this easily exceeds this limit.
This could easily be an additional column in the template where the value is defaulted when not present.
Hi,
I try to export some entities from a solution and I get the following error:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.InvalidOperationException: Sequence contains no matching element
at System.Linq.Enumerable.First[TSource](IEnumerable`1 source, Func`2 predicate)
at Javista.AttributesFactory.AppCode.MetadataDocManager.ProcessDetails(AttributeMetadata amd, EntityMetadata emd, ExcelWorksheet sheet, Int32 line)
at Javista.AttributesFactory.AppCode.MetadataDocManager.GenerateDocumentation(List`1 emds, String filePath, Boolean loadAllAttributes, BackgroundWorker worker)
at Javista.AttributesFactory.PluginControl.tsbExportEntities_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
XrmToolBox
Assembly Version: 1.2020.4.38
Win32 Version: 1.2020.4.38
CodeBase: file:///C:/XrmToolbox/XrmToolBox.exe
----------------------------------------
Javista.AttributesFactory
Assembly Version: 1.2019.11.2
Win32 Version: 1.2019.11.2
CodeBase: file:///C:/USERS/JELLEVE/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/JAVISTA.ATTRIBUTESFACTORY.DLL
I've modified the supplied Template to allow it to be used to migrate SQL Server table definitions. It's pretty rough atm but I've been using it to bulk create SQL table definitions in Dataverse. The new template is Macro enabled (xlsm), as I needed some helper functions to space on capitals ie FirstName maps to the display name "First Name". Is there any interest in taking a look and improving it to the point where it could be included as an option in the plugin, hopefully, it will save someone else the time it took me to work everything out? I have some things hardcoded atm, like schema prefix, global optionset mapping etc, but I'm sure they could be moved to the ValidationData tab or in a new Config tab etc.
When importing money fields I receive the following error with the standard money settings that are in the excel file: "Value was either too large or too small for an Int32."
I did the following:
This swaped "Display name" to "Description" for some of the attributs!!! Don't see why this happend. Very anoying! Also reimprted the file agin on the process window list the "Display name" was correct. Nobody else did some modifications in the system.
See the files attached before and after:
account edit.zip
Thanks for fixing this!
Hello, i've to build an entity with 3 lookup with account as target. I've tried every combination but the add in will throw an error and only the first lookup will e created.
Steps to reproduce: I am creating a new Money field, and I make the precision to 4 in the spreadsheet (attached). I ran the Process Attributes, then the field is created and put on a form. When a user opens the form, the precision is only 2 decimals. I checked the solution UI, and the field shows 'Currency Precision' in the Precision option set, and it does allow me to change it to 4 decimal places, so I have a work around (not critical).
I am using version 1.2022.11.16 of your fantastic tool !!!!
D365 info:
Server version: 9.1.0007.0005
Client version: 1.4.3672-v91onpremise
example currency precision.zip
Thanks!
Hi !
I've noticed that the template we can download from the XrmToolBox-AttributesFactory v 1.2022.6.15 has a very annoying bug.
In the "DataValidation" sheet, in column A, the list of allowed types is organized in 2 data sets : the 1st one (A2:A15) is sorted in alphabetical order and the second one (A22:A35) is in the order that we used to have.
In the "Attributes" sheet, the values proposed in column K (Field type), according to Type selected in column D, are wrong. For example : if Type is "Whole number", the dropdown of possible Field types lists only "Simple"! I must have the choice to select "Calculated" as well as "Rollup".
If in the "DataValidation" sheet (in range A2:A15) I restore the unordered list of types (I've just overwritten A2:A:15 with values of A22:A35, column K (Field type) works properly.
Thanks in advance for your help and all the best.
Hi MscrmTools!
How can I create a field with two options and set the value because I can't find a place to set it in the template
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.